Lines Matching refs:of

16 	  This option allows you to change some of the ways that
21 	  Some users of more advanced features like NUMA and
38 	  more efficient handling of these holes.  However, the vast
39 	  majority of hardware has quite flat address spaces, and
81 # Both the NUMA code and DISCONTIGMEM use arrays of pg_data_t's
82 # to represent different areas of memory.  This variable allows
98 # consume vast quantities of .bss, so be careful.
164 	  - When the system is booting, node full of hotpluggable memory can
168 	  memory of a node as movable memory so that the whole node can be
209 # that require the use of a sectionid in the page flags.
216 # page_table_lock, so that faults on different parts of the user address
246 	  significantly the number of 2MB contiguous memory blocks that can be
248 	  with the reduced number of transparent huge pages that could be used
250 	  pages enlisted as being part of memory balloon devices avoids the
261 	  Allows the compaction of memory for the allocation of huge pages.
271 	  Allows the migration of the physical location of pages of processes
276 	  allocation instead of reclaiming.
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
334 	  of an application's address space that an app has advised may be
335 	  mergeable.  When it finds pages of identical content, it replaces
348 	  This is the portion of low virtual memory which should be protected
350 	  can help reduce the impact of kernel NULL pointer bugs.
352 	  For most ia64, ppc64 and x86 users with lots of address space
353 	  a value of 65536 is reasonable and should cause no problems.
373 	  even when some of its memory has uncorrected errors. This requires
387 	  of memory on which to store mappings, but it can only ask the system
394 	  if there are a lot of transient processes.
400 	  (/proc/sys/vm/nr_trim_pages) which specifies the minimum number of
404 	  This option specifies the initial value of this option.  The default
405 	  of 1 says that all excess pages should be trimmed.
418 	  allocation, by reducing the number of tlb misses and by speeding
434 	  memory footprint of applications without a guaranteed
443 	  memory footprint of applications without a guaranteed
459 	  Cleancache can be thought of as a page-granularity victim cache
465 	  addressable by the kernel and is of unknown and possibly
483 	  Frontswap is so named because it can be thought of as the opposite
484 	  of a "backing" store for a swap device.  The data is stored into
486 	  addressable by the kernel and is of unknown and possibly
502 	  subsystems to allocate big physically-contiguous blocks of memory.
503 	  CMA reserves a region of memory and allows only movable pages to
520 	int "Maximum count of the CMA areas"
526 	  number of CMA area in the system.
550 	  pages that are in the process of being swapped out and attempts to
556 	  This is marked experimental because it is a new feature (as of
559 	  they have not be fully explored on the large set of potential
624 	  This is the maximum stack size in Megabytes in the VM layout of 32-bit