Lines Matching refs:a

19 	  and a correct option.
23 	  DISCONTIGMEM is a more mature, better tested system,
107 # Architecture platforms which require a two level mem_section in SPARSEMEM
127 	 SPARSEMEM_VMEMMAP uses a virtually mapped memmap to optimise
153 	boolean "Enable to assign a node which has only movable memory"
160 	  Allow a node to have only movable memory.  Pages used by the kernel,
168 	  memory of a node as movable memory so that the whole node can be
175 	  Say Y here if you want to hotplug a whole node.
208 # use a virtual memmap. Disable extended page flags for 32 bit platforms
209 # that require the use of a sectionid in the page flags.
247 	  used within a guest, thus imposing performance penalties associated
275 	  pages as migration can relocate pages to satisfy a huge page
301 # a 32-bit address to OHCI.  So we need to use a bounce pool instead.
305 # and fixing that behavior (a second time; jbd2 doesn't have this problem) is
306 # a major rework effort.  Instead, use the bounce buffer to snapshot pages
336 	  the many instances by a single page with that content, so
340 	  until a program has madvised that an area is MADV_MERGEABLE, and
349 	  from userspace allocation.  Keeping a user from writing to low pages
353 	  a value of 65536 is reasonable and should cause no problems.
372 	  with MCA recovery. This allows a system to continue running
394 	  if there are a lot of transient processes.
399 	  Trimming can be dynamically controlled through a sysctl option
434 	  memory footprint of applications without a guaranteed
440 	  Enabling Transparent Hugepage madvise, will only provide a
443 	  memory footprint of applications without a guaranteed
459 	  Cleancache can be thought of as a page-granularity victim cache
462 	  memory.  So when the PFRA "evicts" a page, it first attempts to use
466 	  time-varying size.  And when a cleancache-enabled
467 	  filesystem wishes to access a page in a file on disk, it first
469 	  the page is copied into the kernel and a disk access is avoided.
470 	  When a transcendent memory driver is available (such as zcache or
471 	  Xen transcendent memory), a significant I/O reduction
473 	  are reduced to a single pointer-compare-against-NULL resulting
474 	  in a negligible performance hit.
484 	  of a "backing" store for a swap device.  The data is stored into
488 	  a significant swap I/O reduction may be achieved.  When none is
489 	  available, all frontswap calls are reduced to a single pointer-
490 	  compare-against-NULL resulting in a negligible performance hit
503 	  CMA reserves a region of memory and allows only movable pages to
505 	  pagecache and when a subsystem requests for contiguous area, the
535 	  This option enables memory changes tracking by introducing a
537 	  into a page just as regular dirty bit, but unlike the latter
551 	  compress them into a dynamically allocated RAM-based memory pool.
552 	  This can result in a significant I/O reduction on swap device and,
556 	  This is marked experimental because it is a new feature (as of
576 	  deterministic reclaim properties that make it preferable to a higher
584 	  zsmalloc is a slab-based memory allocator designed to store
586 	  in order to reduce fragmentation.  However, this results in a
587 	  non-standard allocator interface where a handle, not a pointer, is
595 	  By default, zsmalloc uses a copy-based object mapping method to
596 	  access allocations that span two pages. However, if a particular
628 	  changed to a smaller value in which case that is used.