Lines Matching refs: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
36 memory systems, over FLATMEM. These systems have holes
52 memory hotplug systems. This is normal.
82 # to represent different areas of memory. This variable allows
153 bool "Enable to assign a node which has only movable memory"
160 Allow a node to have only movable memory. Pages used by the kernel,
162 memory device cannot be hotplugged. This option allows the following
164 - When the system is booting, node full of hotpluggable memory can
165 be arranged to have only movable memory so that the whole node can
168 memory of a node as movable memory so that the whole node can be
171 Users who don't use the memory hotplug feature are fine with this
173 don't online memory as movable.
176 Say N here if you want kernel to use memory on all nodes evenly.
179 # Only be set on architectures that have completely implemented memory hotplug
187 bool "Allow for memory hot-add"
197 bool "Allow for memory hot remove"
234 # support for memory balloon
239 # support for memory balloon compaction
241 bool "Allow for balloon memory compaction/migration"
246 significantly the number of 2MB contiguous memory blocks that can be
249 by the guest workload. Allowing the compaction & migration for memory
250 pages enlisted as being part of memory balloon devices avoids the
251 scenario aforementioned and helps improving memory defragmentation.
254 # support for memory compaction
256 bool "Allow for memory compaction"
261 Allows the compaction of memory for the allocation of huge pages.
295 the full range of memory available to the CPU. Enabled
300 # have more than 4GB of memory, but we don't currently use the IOTLB to present
338 saving memory until one or another app needs to modify the content.
349 This is the portion of low virtual memory which should be protected
369 bool "Enable recovery from hardware memory errors"
372 Enables code to recover from some memory failures on systems
374 even when some of its memory has uncorrected errors. This requires
375 special hardware support and typically ECC memory.
388 of memory on which to store mappings, but it can only ask the system
418 applications by speeding up page faults during memory
422 If memory constrained on embedded, you may want to say N.
435 memory footprint of applications without a guaranteed
444 memory footprint of applications without a guaranteed
463 memory. So when the PFRA "evicts" a page, it first attempts to use
465 "transcendent memory", memory that is not directly accessible or
471 When a transcendent memory driver is available (such as zcache or
472 Xen transcendent memory), a significant I/O reduction
486 "transcendent memory", memory that is not directly accessible or
488 time-varying size. When space in transcendent memory is available,
503 subsystems to allocate big physically-contiguous blocks of memory.
504 CMA reserves a region of memory and allows only movable pages to
505 be allocated from it. This way, the kernel can use the memory for
538 bool "Track memory changes"
542 This option enables memory changes tracking by introducing a
558 compress them into a dynamically allocated RAM-based memory pool.
564 v3.11) that interacts heavily with memory reclaim. While these
565 interactions don't cause any known issues on simple memory setups,
570 tristate "Common API for compressed memory storage"
573 Compressed memory storage API. This allows using either zbud or
591 zsmalloc is a slab-based memory allocator designed to store
592 compressed RAM pages. zsmalloc uses virtual memory mapping
633 and metag arch). The stack will be located at the highest memory