Home
last modified time | relevance | path

Searched +full:locality +full:- +full:specific (Results 1 – 17 of 17) sorted by relevance

/Documentation/core-api/
Dworkqueue.rst33 thread system-wide. A single MT wq needed to keep around the same
60 * Use per-CPU unified worker pools shared by all wq to provide
83 called worker-pools.
85 The cmwq design differentiates between the user-facing workqueues that
87 which manages worker-pools and processes the queued work items.
89 There are two worker-pools, one for normal work items and the other
91 worker-pools to serve work items queued on unbound workqueues - the
98 things like CPU locality, concurrency limits, priority and more. To
102 When a work item is queued to a workqueue, the target worker-pool is
104 and appended on the shared worklist of the worker-pool. For example,
[all …]
/Documentation/networking/
Dscaling.rst1 .. SPDX-License-Identifier: GPL-2.0
13 multi-processor systems.
17 - RSS: Receive Side Scaling
18 - RPS: Receive Packet Steering
19 - RFS: Receive Flow Steering
20 - Accelerated Receive Flow Steering
21 - XPS: Transmit Packet Steering
28 (multi-queue). On reception, a NIC can send different packets to different
33 generally known as “Receive-side Scaling” (RSS). The goal of RSS and
35 Multi-queue distribution can also be used for traffic prioritization, but
[all …]
/Documentation/vm/
Dpage_migration.rst44 Documentation/admin-guide/cgroup-v1/cpusets.rst).
45 Cpusets allows the automation of process locality. If a task is moved to
148 Non-LRU page migration
152 for NUMA, compaction who want to create high-order page is also main customer.
155 *LRU* pages. However, there are potential non-lru pages which can be migrated
156 in drivers, for example, zsmalloc, virtio-balloon pages.
158 For virtio-balloon pages, some parts of migration code path have been hooked
159 up and added virtio-balloon specific functions to intercept migration logics.
160 It's too specific to a driver so other drivers who want to make their pages
161 movable would have to add own specific hooks in migration path.
[all …]
/Documentation/devicetree/bindings/interrupt-controller/
Darm,gic-v3.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/arm,gic-v3.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Marc Zyngier <marc.zyngier@arm.com>
15 Software Generated Interrupts (SGI), and Locality-specific Peripheral
19 - $ref: /schemas/interrupt-controller.yaml#
24 - items:
25 - enum:
26 - qcom,msm8996-gic-v3
[all …]
/Documentation/arm64/
Darm-acpi.rst22 industry-standard ARMv8 servers, they also apply to more than one operating
24 ACPI and Linux only, on an ARMv8 system -- that is, what Linux expects of
29 ----------------
32 exist in Linux for describing non-enumerable hardware, after all. In this
39 - ACPI’s byte code (AML) allows the platform to encode hardware behavior,
44 - ACPI’s OSPM defines a power management model that constrains what the
45 platform is allowed to do into a specific model, while still providing
48 - In the enterprise server environment, ACPI has established bindings (such
54 - Choosing a single interface to describe the abstraction between a platform
60 - The new ACPI governance process works well and Linux is now at the same
[all …]
Dacpi_object_usage.rst16 - Required: DSDT, FADT, GTDT, MADT, MCFG, RSDP, SPCR, XSDT
18 - Recommended: BERT, EINJ, ERST, HEST, PCCT, SSDT
20 - Optional: BGRT, CPEP, CSRT, DBG2, DRTM, ECDT, FACS, FPDT, IORT,
24 - Not supported: BOOT, DBGP, DMAR, ETDT, HPET, IBFT, IVRS, LPIT,
47 Optional, not currently supported, with no real use-case for an
55 time as ARM-compatible hardware is available, and the specification
123 UEFI-based; if it is UEFI-based, this table may be supplied. When this
139 the hardware reduced profile, and only 64-bit address fields will
156 filled in properly - that the PSCI_COMPLIANT flag is set and that
157 PSCI_USE_HVC is set or unset as needed (see table 5-37).
[all …]
/Documentation/filesystems/
Dsquashfs.txt4 Squashfs is a compressed read-only filesystem for Linux.
10 Squashfs is intended for general read-only filesystem use, for archival
15 Mailing list: squashfs-devel@lists.sourceforge.net
19 ----------------------
34 Tail-end packing (fragments): yes no
39 32-bit uids/gids: yes no
51 -----------------
53 As squashfs is a read-only filesystem, the mksquashfs program must be used to
58 The squashfs-tools development tree is now located on kernel.org
59 git://git.kernel.org/pub/scm/fs/squashfs/squashfs-tools.git
[all …]
Dproc.txt1 ------------------------------------------------------------------------------
3 ------------------------------------------------------------------------------
9 ------------------------------------------------------------------------------
11 Kernel version 2.4.0-test11-pre4
12 ------------------------------------------------------------------------------
16 -----------------
23 1.1 Process-Specific Subdirectories
35 3 Per-Process Parameters
36 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj - Adjust the oom-killer
38 3.2 /proc/<pid>/oom_score - Display current oom-killer score
[all …]
Df2fs.txt2 WHAT IS Flash-Friendly File System (F2FS)?
5 NAND flash memory-based storage devices, such as SSD, eMMC, and SD cards, have
11 F2FS is a file system exploiting NAND flash memory-based storage devices, which
12 is based on Log-structured File System (LFS). The design has been focused on
16 Since a NAND flash memory-based storage device shows different characteristic
18 F2FS and its tools support various parameters not only for configuring on-disk
23 >> git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git
26 >> linux-f2fs-devel@lists.sourceforge.net
32 Log-structured File System (LFS)
33 --------------------------------
[all …]
/Documentation/admin-guide/sysctl/
Dvm.rst13 ------------------------------------------------------------------------------
27 - admin_reserve_kbytes
28 - block_dump
29 - compact_memory
30 - compact_unevictable_allowed
31 - dirty_background_bytes
32 - dirty_background_ratio
33 - dirty_bytes
34 - dirty_expire_centisecs
35 - dirty_ratio
[all …]
Dkernel.rst13 ------------------------------------------------------------------------------
27 - acct
28 - acpi_video_flags
29 - auto_msgmni
30 - bootloader_type [ X86 only ]
31 - bootloader_version [ X86 only ]
32 - cap_last_cap
33 - core_pattern
34 - core_pipe_limit
35 - core_uses_pid
[all …]
/Documentation/
Drbtree.txt2 Red-black Trees (rbtree) in Linux
9 What are red-black trees, and what are they for?
10 ------------------------------------------------
12 Red-black trees are a type of self-balancing binary search tree, used for
16 be easily traversed in order, and must be tuned for a specific size and
19 Red-black trees are similar to AVL trees, but provide faster real-time bounded
26 There are a number of red-black trees in use in the kernel.
29 The high-resolution timer code uses an rbtree to organize outstanding
31 red-black tree. Virtual memory areas (VMAs) are tracked with red-black
38 Linux Weekly News article on red-black trees
[all …]
/Documentation/admin-guide/
Dkernel-parameters.txt5 force -- enable ACPI if default was off
6 on -- enable ACPI but allow fallback to DT [arm64]
7 off -- disable ACPI if default was on
8 noirq -- do not use ACPI for IRQ routing
9 strict -- Be less tolerant of platforms that are not
11 rsdt -- prefer RSDT over (default) XSDT
12 copy_dsdt -- copy DSDT to memory
27 If set to vendor, prefer vendor specific driver
56 Documentation/firmware-guide/acpi/debug.rst for more information about
119 Disable auto-serialization of AML methods
[all …]
/Documentation/admin-guide/cgroup-v1/
Dmemory.rst18 we call it "memory cgroup". When you see git-log and source code, you'll
30 Memory-hungry applications can be isolated and limited to a smaller
42 Current Status: linux-2.6.34-mmotm(development version of 2010/April)
46 - accounting anonymous pages, file caches, swap caches usage and limiting them.
47 - pages are linked to per-memcg LRU exclusively, and there is no global LRU.
48 - optionally, memory+swap usage can be accounted and limited.
49 - hierarchical accounting
50 - soft limit
51 - moving (recharging) account at moving a task is selectable.
52 - usage threshold notifier
[all …]
/Documentation/RCU/Design/Data-Structures/
DData-Structures.html1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
5 <meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
16 <li> <a href="#Data-Structure Relationships">
17 Data-Structure Relationships</a>
28 <li> <a href="#RCU-Specific Fields in the task_struct Structure">
29 RCU-Specific Fields in the <tt>task_struct</tt> Structure</a>
34 <h3><a name="Data-Structure Relationships">Data-Structure Relationships</a></h3>
55 which results in a three-level <tt>rcu_node</tt> tree.
59 </p><p>The purpose of this combining tree is to allow per-CPU events
60 such as quiescent states, dyntick-idle transitions,
[all …]
/Documentation/RCU/
DRTFP.txt4 This document describes RCU-related publications, and is followed by
19 with short-lived threads, such as the K42 research operating system.
20 However, Linux has long-lived tasks, so more is needed.
23 serialization, which is an RCU-like mechanism that relies on the presence
27 that these overheads were not so expensive in the mid-80s. Nonetheless,
28 passive serialization appears to be the first deferred-destruction
30 has lapsed, so this approach may be used in non-GPL software, if desired.
34 In 1987, Rashid et al. described lazy TLB-flush [RichardRashid87a].
36 this paper helped inspire the update-side batching used in the later
38 a description of Argus that noted that use of out-of-date values can
[all …]
/Documentation/RCU/Design/Requirements/
DRequirements.html1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
5 <meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
20 Read-copy update (RCU) is a synchronization mechanism that is often
21 used as a replacement for reader-writer locking.
23 which means that RCU's read-side primitives can be exceedingly fast
33 of as an informal, high-level specification for RCU.
49 <li> <a href="#Fundamental Non-Requirements">Fundamental Non-Requirements</a>
52 <li> <a href="#Quality-of-Implementation Requirements">
53 Quality-of-Implementation Requirements</a>
56 <li> <a href="#Software-Engineering Requirements">
[all …]