| /linux-6.1.9/mm/damon/ |
| D | paddr.c | 86 bool accessed; member
95 result->accessed = false; in __damon_pa_young()
100 result->accessed = pte_young(*pvmw.pte) || in __damon_pa_young()
105 result->accessed = pmd_young(*pvmw.pmd) || in __damon_pa_young()
113 if (result->accessed) { in __damon_pa_young()
120 return !result->accessed; in __damon_pa_young()
129 .accessed = false, in damon_pa_young()
144 result.accessed = false; in damon_pa_young()
146 result.accessed = true; in damon_pa_young()
165 return result.accessed; in damon_pa_young()
|
| D | Kconfig | 91 that not accessed for a long time (cold) using DAMON and reclaim
103 protect frequently accessed (hot) pages while rarely accessed (cold)
|
| /linux-6.1.9/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.1.9/Documentation/devicetree/bindings/fsi/ |
| D | ibm,p9-occ.txt | 4 This is the binding for the P9 or P10 On-Chip Controller accessed over FSI from
6 nodes. The OCC is not an FSI slave device itself, rather it is accessed
|
| /linux-6.1.9/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
|
| D | frontend.rst | 30 The frontend can be accessed through ``/dev/dvb/adapter?/frontend?``.
31 Data types and ioctl definitions can be accessed by including
|
| /linux-6.1.9/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-file_endian.txt | 7 raw data being accessed by the tep handler.
27 being accessed by the tep handler. The _tep_ argument is trace event parser
31 accessed by the tep handler. The _tep_ argument is trace event parser context.
|
| /linux-6.1.9/drivers/staging/media/deprecated/saa7146/av7110/ |
| D | audio.rst | 10 TV hardware. It can be accessed through ``/dev/dvb/adapter?/audio?``. Data
11 types and ioctl definitions can be accessed by including
|
| D | video.rst | 10 TV hardware. It can be accessed through **/dev/dvb/adapter0/video0**. Data
11 types and ioctl definitions can be accessed by including
|
| /linux-6.1.9/Documentation/devicetree/bindings/arm/amlogic/ |
| D | amlogic,meson-mx-secbus2.yaml | 16 The registers can be accessed directly when not running in "secure mode".
17 When "secure mode" is enabled then these registers have to be accessed
|
| /linux-6.1.9/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``
116 generation when it finds them accessed through page tables; the
124 the aging clears the accessed bit and updates the gen counter of the
137 accessed through page tables and updated its gen counter. It also
139 was accessed multiple times through file descriptors and the feedback
|
| /linux-6.1.9/arch/alpha/lib/ |
| D | memchr.S | 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 | 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.1.9/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.
|
| /linux-6.1.9/Documentation/admin-guide/mm/ |
| D | idle_page_tracking.rst | 11 accessed by a workload and which are idle. This information can be useful for
32 A page is considered idle if it has not been accessed since it was marked idle
33 (for more details on what "accessed" actually means see the :ref:`Implementation
84 considered referenced if it has been recently accessed via a process address
86 set, or marked accessed explicitly by the kernel (see mark_page_accessed()). The
96 - a page is accessed by a device driver using get_user_pages()
|
| 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.1.9/Documentation/devicetree/bindings/ |
| D | resource-names.txt | 2 normally accessed by index. However, some devices will have multiple
3 values which are more naturally accessed by name. Device nodes can
|
| /linux-6.1.9/Documentation/i2c/ |
| D | i2c-topology.rst | 17 that has to be operated before the device can be accessed.
207 When any device is accessed, all other devices are locked out for
231 When device D1 is accessed, accesses to D2 are locked out for the
254 When device D1 is accessed, accesses to D2 and D3 are locked out
288 When D1 is accessed, accesses to D2 are locked out for the full
293 When D3 or D4 are accessed, everything else is locked out. For D3
318 When D1 is accessed, accesses to D2, D3 and D4 are locked out. But
342 When any device is accessed, accesses to all other devices are locked
366 When D1 or D2 are accessed, accesses to D3 and D4 are locked out while
367 accesses to D5 may interleave. When D3 or D4 are accessed, accesses to
|
| /linux-6.1.9/arch/mips/net/ |
| D | bpf_jit_comp.h | 82 u32 accessed; /* Bit mask of read eBPF registers */ member
129 ctx->accessed |= BIT(reg); in access_reg()
|
| /linux-6.1.9/Documentation/arm64/ |
| D | tagged-address-abi.rst | 46 1. User addresses not accessed by the kernel but used for address space
67 2. User addresses accessed by the kernel (e.g. ``write()``). This ABI
119 indirectly as arguments to be accessed by the kernel.
122 indirectly as arguments to be accessed by the kernel.
|
| /linux-6.1.9/Documentation/ABI/stable/ |
| D | sysfs-devices-node | 122 This node's read bandwidth in MB/s when accessed from
129 This node's read latency in nanoseconds when accessed
136 This node's write bandwidth in MB/s when accessed from
164 The number of bytes accessed from the next cache level on a
|
| /linux-6.1.9/Documentation/devicetree/bindings/hwmon/ |
| D | apm-xgene-hwmon.txt | 3 APM X-Gene SOC sensors are accessed over the "SLIMpro" mailbox.
|
| /linux-6.1.9/Documentation/devicetree/bindings/i2c/ |
| D | i2c-xgene-slimpro.txt | 3 An I2C controller accessed over the "SLIMpro" mailbox.
|
| /linux-6.1.9/Documentation/virt/kvm/devices/ |
| D | arm-vgic-v3.rst | 86 __u32 value. 64-bit registers must be accessed by separately accessing the
100 differently when accessed via this interface compared to their
105 redistributor is accessed. The mpidr is ignored for the distributor.
148 and ISPENDR registers.) For a level triggered interrupt the value accessed
192 All system regs accessed through this API are (rw, 64-bit) and
199 Error -ENXIO is returned when accessed in AArch32 mode.
|