Searched full:accessed (Results 1 – 25 of 356) sorted by relevance
12345678910>>...15
| /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
|
| /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
|
| /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
|
| /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.
|
| /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
|
| /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
|
| /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.
|
| /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
|
| D | common-properties.txt | 15 know the peripheral always needs to be accessed in big endian (BE) mode.
18 peripheral always needs to be accessed in little endian (LE) mode.
|
| /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.
162 Fan speed sensors can be accessed by selecting subfeature ``0x00``. The output data contains
191 the embedded controller memory is accessed by the ACPI AML code. The driver also supports a
|
| /Documentation/devicetree/bindings/bus/ |
| D | fsl,imx8qxp-pixel-link-msi-bus.yaml | 20 connected to the bus can be accessed. Also, the bus is part of a power
22 be accessed.
26 Status Registers (CSR) module, are accessed through the bus.
30 So, the controller's registers cannot be accessed by SCFW user. Hence,
|
| /Documentation/arch/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.
|
| /Documentation/translations/zh_CN/mm/damon/ |
| D | design.rst | 68 物理和虚拟地址空间的实现都使用PTE Accessed-bit进行基本访问检查。唯一的区别在于从地址中
94 if accessed(page):
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-xgene-slimpro.txt | 3 An I2C controller accessed over the "SLIMpro" mailbox.
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | apm-xgene-hwmon.txt | 3 APM X-Gene SOC sensors are accessed over the "SLIMpro" mailbox.
|
| /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
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | snps,arc700-intc.txt | 15 intc accessed via the special ARC AUX register interface, hence "reg" property
|
| D | snps,archs-intc.txt | 12 intc accessed via the special ARC AUX register interface, hence "reg" property
|
| /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
|
| /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 …]
|
| /Documentation/bpf/ |
| D | maps.rst | 10 maps are accessed from BPF programs via BPF helpers which are documented in the
13 BPF maps are accessed from user space via the ``bpf`` syscall, which provides
|
| /Documentation/networking/devlink/ |
| D | devlink-region.rst | 11 region can then be accessed via the devlink region interface.
13 Region snapshots are collected by the driver, and can be accessed via read
|
12345678910>>...15