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
224 used within a guest, thus imposing performance penalties associated
243 disable this option unless there really is a strong reason for
259 pages as migration can relocate pages to satisfy a huge page
283 # a 32-bit address to OHCI. So we need to use a bounce pool instead.
312 the many instances by a single page with that content, so
316 until a program has madvised that an area is MADV_MERGEABLE, and
325 from userspace allocation. Keeping a user from writing to low pages
329 a value of 65536 is reasonable and should cause no problems.
349 with MCA recovery. This allows a system to continue running
371 if there are a lot of transient processes.
376 Trimming can be dynamically controlled through a sysctl option
412 memory footprint of applications without a guaranteed
418 Enabling Transparent Hugepage madvise, will only provide a
421 memory footprint of applications without a guaranteed
453 Cleancache can be thought of as a page-granularity victim cache
456 memory. So when the PFRA "evicts" a page, it first attempts to use
460 time-varying size. And when a cleancache-enabled
461 filesystem wishes to access a page in a file on disk, it first
463 the page is copied into the kernel and a disk access is avoided.
464 When a transcendent memory driver is available (such as zcache or
465 Xen transcendent memory), a significant I/O reduction
467 are reduced to a single pointer-compare-against-NULL resulting
468 in a negligible performance hit.
478 of a "backing" store for a swap device. The data is stored into
482 a significant swap I/O reduction may be achieved. When none is
483 available, all frontswap calls are reduced to a single pointer-
484 compare-against-NULL resulting in a negligible performance hit
497 CMA reserves a region of memory and allows only movable pages to
499 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
586 page. It is a ZBUD derivative so the simplicity and determinism are
594 zsmalloc is a slab-based memory allocator designed to store
596 in order to reduce fragmentation. However, this results in a
597 non-standard allocator interface where a handle, not a pointer, is
605 By default, zsmalloc uses a copy-based object mapping method to
606 access allocations that span two pages. However, if a particular
638 changed to a smaller value in which case that is used.
654 Ordinarily all struct pages are initialised during early boot in a
655 single thread. On very large machines this can take a considerable
657 a subset of memmap at boot and then initialise the rest in parallel
659 has a potential performance impact on processes running early in the
669 not been touched during a given period of time. This information can
671 within a compute cluster.
691 "device-physical" addresses which is needed for using a DAX
715 bool "HMM mirror CPU page table into a device page table"
719 Select HMM_MIRROR if you want to mirror range of the CPU page table of a
720 process into a device page table. Here, mirror means "keep synchronized".