Lines Matching full:memory
6 prompt "Memory model"
13 bool "Flat Memory"
17 Linux manages its memory internally. Most users will
22 memory hotplug may have different options here.
24 but is incompatible with memory hotplug and may suffer
26 "Sparse Memory" and "Discontiguous Memory", choose
27 "Discontiguous Memory".
29 If unsure, choose this option (Flat Memory) over any other.
32 bool "Discontiguous Memory"
36 memory systems, over FLATMEM. These systems have holes
45 If unsure, choose "Flat Memory" over this option.
48 bool "Sparse Memory"
52 memory hotplug systems. This is normal.
55 "Discontiguous Memory". This option provides some potential
59 If unsure, choose "Discontiguous Memory" or "Flat Memory"
82 # to represent different areas of memory. This variable allows
123 bool "Sparse Memory virtual memmap"
145 bool "Allow for memory hot-add"
155 bool "Allow for memory hot remove"
187 # support for memory compaction
189 bool "Allow for memory compaction"
193 Allows the compaction of memory for the allocation of huge pages.
243 saving memory until one or another app needs to modify the content.
254 This is the portion of low virtual memory which should be protected
274 bool "Enable recovery from hardware memory errors"
276 Enables code to recover from some memory failures on systems
278 even when some of its memory has uncorrected errors. This requires
279 special hardware support and typically ECC memory.
292 of memory on which to store mappings, but it can only ask the system
322 applications by speeding up page faults during memory
326 If memory constrained on embedded, you may want to say N.
339 memory footprint of applications without a guaranteed
348 memory footprint of applications without a guaranteed
367 memory. So when the PFRA "evicts" a page, it first attempts to use
369 "transcendent memory", memory that is not directly accessible or
375 When a transcendent memory driver is available (such as zcache or
376 Xen transcendent memory), a significant I/O reduction