Lines Matching +full:address +full:- +full:address +full:- +full:data

7 systems from MMU-less microcontrollers to supercomputers. The memory
12 address to a physical address.
23 address ranges. Besides, different CPU architectures, and even
25 of how these address ranges are defined.
33 protection and controlled sharing of data between processes.
36 address. When the CPU decodes an instruction that reads (or
38 address encoded in that instruction to a `physical` address that the
49 translation from a virtual address used by programs to the physical
50 memory address. The page tables are organized hierarchically.
56 register. When the CPU performs the address translation, it uses this
58 virtual address are used to index an entry in the top level page
60 hierarchy with the next bits of the virtual address as the index to
61 that level page table. The lowest bits in the virtual address define
67 The address translation requires several memory accesses and memory
69 processor cycles on the address translation, CPUs maintain a cache of
80 improves TLB hit-rate and thus improves overall system performance.
85 store. For the files created in this filesystem the data resides in
87 Documentation/admin-guide/mm/hugetlbpage.rst.
94 name. See Documentation/admin-guide/mm/transhuge.rst for more details
108 permanently mapped into kernel's address space and ZONE_NORMAL will
118 Many multi-processor machines are NUMA - Non-Uniform Memory Access -
126 Documentation/admin-guide/mm/numa_memory_policy.rst.
131 The physical memory is volatile and the common case for getting data
133 data is put into the `page cache` to avoid expensive disk access on
134 the subsequent reads. Similarly, when one writes to a file, the data
138 the file contents on the device with the updated data.
150 physical page will be allocated to hold the written data. The page
158 different types of data. It can be kernel internal data structures,
159 DMA'able buffers for device drivers use, data read from a filesystem,
164 because they cache the data available elsewhere, for instance, on a
169 In most cases, the pages holding internal kernel data and used as DMA
172 circumstances, even pages occupied with kernel data structures can be
173 reclaimed. For instance, in-memory caches of filesystem metadata can
174 be re-read from the storage device and therefore it is possible to
186 asynchronously scan memory pages and either just free them if the data
189 more and reaches another threshold - min watermark - an allocation