| /linux-6.12.1/Documentation/admin-guide/mm/ |
| D | idle_page_tracking.rst | 9 accessed by a workload and which are idle. This information can be useful for
30 A page is considered idle if it has not been accessed since it was marked idle
31 (for more details on what "accessed" actually means see the :ref:`Implementation
81 considered referenced if it has been recently accessed via a process address
82 space, in which case one or more PTEs it is mapped to will have the Accessed bit
83 set, or marked accessed explicitly by the kernel (see mark_page_accessed()). The
93 - a page is accessed by a device driver using get_user_pages()
104 When a page is marked idle, the Accessed bit must be cleared in all PTEs it is
107 as noted above, uses the Accessed bit to promote actively referenced pages, one
108 more page flag is introduced, the Young flag. When the PTE Accessed bit is
[all …]
|
| D | multigen_lru.rst | 39 0x0002 Clearing the accessed bit in leaf page table entries in large
44 whose accessed bits can be otherwise cleared by fewer larger
46 0x0004 Clearing the accessed bit in non-leaf page table entries as
106 accessed over different time intervals for each memcg and node.
117 Each bin contains an estimated number of pages that have been accessed
|
| /linux-6.12.1/mm/damon/ |
| D | paddr.c | 93 bool *accessed = arg; in damon_folio_young_one() local
96 *accessed = false; in damon_folio_young_one()
100 *accessed = pte_young(ptep_get(pvmw.pte)) || in damon_folio_young_one()
105 *accessed = pmd_young(pmdp_get(pvmw.pmd)) || in damon_folio_young_one()
112 if (*accessed) { in damon_folio_young_one()
118 /* If accessed, stop walking */ in damon_folio_young_one()
119 return *accessed == false; in damon_folio_young_one()
124 bool accessed = false; in damon_folio_young() local
126 .arg = &accessed, in damon_folio_young()
148 return accessed; in damon_folio_young()
[all …]
|
| D | Kconfig | 109 that not accessed for a long time (cold) using DAMON and reclaim
121 protect frequently accessed (hot) pages while rarely accessed (cold)
|
| /linux-6.12.1/tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/ |
| D | memory.json | 8 …. Note that errors are only detected when the actual protected memory is accessed by an operation."
24 …latency, due to the alignment of the address and the size of data being accessed, which results in…
28 …nal latency, due to the alignment of the address and size of data being accessed, which results in…
32 …nal latency, due to the alignment of the address and size of data being accessed incurred addition…
|
| /linux-6.12.1/Documentation/mm/ |
| D | multigen_lru.rst | 30 accessed bit. A rmap walk targets a single page and does not try to
61 channel is higher due to the approximation of the accessed bit.
98 Each generation is divided into multiple tiers. A page accessed ``N``
117 generation when it finds them accessed through page tables; the
125 the aging clears the accessed bit and updates the gen counter of the
138 accessed through page tables and updated its gen counter. It also
140 was accessed multiple times through file descriptors and the feedback
184 and clear the accessed bit) can be expensive because pages from
|
| /linux-6.12.1/Documentation/driver-api/ |
| D | edac.rst | 54 The data accessed by the memory controller is contained into one dimm
62 The data size accessed by the memory controller is interlaced into two
63 dimms, accessed at the same time. E. g. if the DIMM is 64 bits-wide (72
70 accessed. Common chip-select rows for single channel are 64 bits, for
86 sets of memory devices. The two rows cannot be accessed concurrently.
93 of memory devices. The two rows cannot be accessed concurrently.
196 GPU nodes can be accessed the same way as the data fabric on CPU nodes.
|
| /linux-6.12.1/drivers/net/ethernet/intel/e1000/ |
| D | e1000_hw.c | 90 * @hw: Struct containing variables accessed by shared code
129 * @hw: Struct containing variables accessed by shared code
223 * @hw: Struct containing variables accessed by shared code
331 * @hw: Struct containing variables accessed by shared code
372 * @hw: Struct containing variables accessed by shared code
517 * @hw: Struct containing variables accessed by shared code
641 * @hw: Struct containing variables accessed by shared code.
678 * @hw: Struct containing variables accessed by shared code
793 * @hw: Struct containing variables accessed by shared code
937 * @hw: Struct containing variables accessed by shared code
[all …]
|
| /linux-6.12.1/arch/arm64/kernel/ |
| D | image-vars.h | 18 * accessed by the stub, so provide some aliases to make them accessible.
79 * accessed by it, therefore provide aliases to make them linkable.
80 * Do not include symbols which may not be safely accessed under hypervisor
95 /* Global kernel state accessed by nVHE hyp code. */
|
| /linux-6.12.1/fs/freevxfs/ |
| D | vxfs_inode.h | 81 __fs32 vdi_atime; /* Last time accessed - sec */
82 __fs32 vdi_autime; /* Last time accessed - usec */
137 __u32 vii_atime; /* Last time accessed - sec */
138 __u32 vii_autime; /* Last time accessed - usec */
|
| /linux-6.12.1/arch/x86/kvm/mmu/ |
| D | tdp_iter.h | 38 * handler, and Accessed and Dirty bits can be set by the CPU.
40 * Note, non-leaf SPTEs do have Accessed bits and those bits are
41 * technically volatile, but KVM doesn't consume the Accessed bit of
43 * logic needs to be reassessed if KVM were to use non-leaf Accessed
|
| /linux-6.12.1/arch/alpha/lib/ |
| D | memchr.S | 22 - memory accessed as aligned quadwords only
31 - only minimum number of quadwords may be accessed
120 # Make $18 point to last quad to be accessed (the
127 # At least two quads remain to be accessed.
133 # At least three quads remain to be accessed
|
| D | ev6-memchr.S | 9 * - memory accessed as aligned quadwords only
18 * - only minimum number of quadwords may be accessed
139 # Make $18 point to last quad to be accessed (the
145 # At least two quads remain to be accessed.
150 # At least three quads remain to be accessed
|
| /linux-6.12.1/drivers/net/ethernet/atheros/atl1e/ |
| D | atl1e_hw.c | 136 * hw - Struct containing variables accessed by shared code
169 * hw - Struct containing variables accessed by shared code
197 * hw - Struct containing variables accessed by shared code
230 * hw - Struct containing variables accessed by shared code
281 * hw - Struct containing variables accessed by shared code
370 * hw - Struct containing variables accessed by shared code
499 * hw - Struct containing variables accessed by shared code
554 * hw - Struct containing variables accessed by shared code
579 * hw - Struct containing variables accessed by shared code
|
| /linux-6.12.1/fs/ |
| D | backing-file.c | 202 if (ctx->accessed) in backing_file_read_iter()
203 ctx->accessed(ctx->user_file); in backing_file_read_iter()
288 if (ctx->accessed) in backing_file_splice_read()
289 ctx->accessed(ctx->user_file); in backing_file_splice_read()
345 if (ctx->accessed) in backing_file_mmap()
346 ctx->accessed(ctx->user_file); in backing_file_mmap()
|
| /linux-6.12.1/include/linux/iio/ |
| D | buffer-dma.h | 54 /* May only be accessed by the owner of the block */
59 * Set during allocation, constant thereafter. May be accessed read-only
67 /* Must not be accessed outside the core. */
70 * Must not be accessed outside the core. Access needs to hold
|
| /linux-6.12.1/Documentation/wmi/devices/ |
| D | msi-wmi-platform.rst | 132 happen when a invalid byte field is ultimately accessed), all methods require a 32 byte input
135 The input buffer contains a single byte to select the subfeature to be accessed and 31 bytes of
136 input data, the meaning of which depends on the subfeature being accessed.
139 and 31 bytes of output data, the meaning if which depends on the subfeature being accessed.
158 Fan speed sensors can be accessed by selecting subfeature ``0x00``. The output data contains
187 the embedded controller memory is accessed by the ACPI AML code. The driver also supports a
|
| /linux-6.12.1/Documentation/dev-tools/ |
| D | kasan.rst | 244 where the accessed memory was allocated (in case a slab object was accessed),
246 bug report). Next comes a description of the accessed slab object and the
247 information about the accessed memory page.
249 In the end, the report shows the memory state around the accessed address.
253 granules that surround the accessed address.
266 that the accessed address is partially accessible.
269 the accessed address (see the `Implementation details`_ section).
356 that is being accessed is equal to the tag of the pointer that is used to access
384 access, hardware makes sure that the tag of the memory that is being accessed is
410 accessed by the kernel. Therefore, KASAN only maps real shadow for certain
|
| /linux-6.12.1/arch/parisc/include/uapi/asm/ |
| D | ptrace.h | 21 * It can be accessed through PTRACE_PEEKUSR/PTRACE_POKEUSR only.
48 * It can be accessed through PTRACE_GETREGSET with NT_PRSTATUS
73 * It can be accessed through PTRACE_GETREGSET with NT_PRFPREG
|
| /linux-6.12.1/Documentation/admin-guide/blockdev/drbd/ |
| D | data-structure-v9.rst | 30 In this table, horizontally, devices can be accessed from resources by their
31 volume number. Likewise, peer_devices can be accessed from connections by
37 devices can be accessed by their minor device number via the drbd_devices idr.
|
| /linux-6.12.1/Documentation/devicetree/bindings/mtd/ |
| D | amlogic,meson-nand.yaml | 71 configuration must be used because it is accessed by the ROM
78 Interval between pages, accessed by the ROM code. For example
79 we have 8 pages [0, 7]. Pages 0,2,4,6 are accessed by the
|
| /linux-6.12.1/Documentation/userspace-api/media/dvb/ |
| D | ca.rst | 10 can be accessed through ``/dev/dvb/adapter?/ca?``. Data types and ioctl
11 definitions can be accessed by including ``linux/dvb/ca.h`` in your
|
| D | demux.rst | 14 It can be accessed through ``/dev/adapter?/demux?``. Data types and
15 ioctl definitions can be accessed by including ``linux/dvb/dmx.h`` in
|
| /linux-6.12.1/include/linux/ |
| D | seccomp_types.h | 17 * accessed without locking during system call entry.
19 * @filter must only be accessed from the context of current as there
|
| /linux-6.12.1/Documentation/mm/damon/ |
| D | design.rst | 96 mapped to the physical memory and accessed. Thus, tracking the unmapped
121 PTE Accessed-bit Based Access Check
125 Accessed-bit for basic access checks. Only one difference is the way of
126 finding the relevant PTE Accessed bit(s) from the address. While the
132 subsystems using the Accessed bits, namely Idle page tracking and the reclaim
162 The output of DAMON says what pages are how frequently accessed for a given
173 if accessed(page):
196 ``sampling interval``, checks whether the page is accessed meanwhile, and
275 paging out memory regions that are not accessed for more than two minutes
414 rarely accessed (colder) memory regions would be prioritized for page-out
[all …]
|