Lines Matching refs:memory

13 of the virtual memory (VM) subsystem of the Linux kernel and
67 The amount of free memory in the system that should be reserved for users
90 Changing this takes effect whenever an application requests memory.
104 all zones are compacted such that free memory is available in contiguous
106 huge pages although processes will also directly compact memory as required.
115 acceptable trade for large contiguous free memory.  Set to 0 to prevent
122 Contains the amount of dirty memory at which the background kernel
127 immediately taken into account to evaluate the dirty memory limits and the
134 Contains, as a percentage of total available memory that contains free pages
138 The total avaiable memory is not equal to total system memory.
144 Contains the amount of dirty memory at which a process generating disk writes
149 account to evaluate the dirty memory limits and the other appears as 0 when
162 of a second.  Data which has been dirty in-memory for longer than this
169 Contains, as a percentage of total available memory that contains free pages
173 The total avaiable memory is not equal to total system memory.
191 memory becomes free.
208 reclaimed by the kernel when memory is needed elsewhere on the system.
227 This parameter affects whether the kernel will compact memory or direct
231 of memory, values towards 1000 imply failures are due to fragmentation and -1
234 The kernel will not compact memory in a zone if the
256 memory more likely. Note that using ZONE_MOVABLE for non-migratable
257 hugepages can do harm to other features like memory hotremove (because
258 memory hotremove expects that memory blocks on ZONE_MOVABLE are always
266 shared memory segment using hugetlb page.
287 the kernel to allow process memory to be allocated from the "lowmem"
288 zone.  This is because that memory could then be pinned via the mlock()
291 And on large highmem machines this lack of reclaimable lowmem memory
297 captured into pinned user memory.
373 This file contains the maximum number of memory map areas a process
388 Control how to kill processes when uncorrected memory error (typically
389 a 2bit error in a memory module) is detected in the background by hardware
416 Enable memory failure recovery (when supported by the platform)
420 0: Always panic on a memory failure.
432 Some minimal amount of memory is needed to satisfy PF_MEMALLOC
453 The process of reclaiming slab memory is currently not node specific
480 of memory userspace processes should not be allowed to write to them.  By
525 'where the memory is allocated from' is controlled by zonelists.
531 This means that a memory allocation request for GFP_KERNEL will
532 get memory from ZONE_DMA only when ZONE_NORMAL is not available.
542 out-of-memory(OOM) of ZONE_DMA because ZONE_DMA is tend to be small.
558 (2) if the DMA zone comprises greater than 50% of the available memory or
559 (3) if any node's DMA zone comprises greater than 70% of its local memory and
560     the amount of local memory is big enough.
578 the memory state information for each one.  Such systems should not
583 OOM killer actually kills a memory-hogging task.
592 out-of-memory situations.
596 selects a rogue memory-hogging task that frees up a large amount of
597 memory when killed.
600 triggered the out-of-memory condition.  This avoids the expensive
623 This value contains a flag that enables memory overcommitment.
626 of free memory left when userspace requests more memory.
629 memory until it actually runs out.
632 policy that attempts to prevent any overcommit of memory.
636 programs that malloc() huge amounts of memory "just-in-case"
678 This enables or disables panic on out-of-memory feature.
684 If this is set to 1, the kernel panics when out-of-memory happens.
686 and those nodes become memory exhaustion status, one process
688 Because other nodes' memory may be free. This means system total status
692 above-mentioned. Even oom happens under memory cgroup, the whole
731 memory pages.  Higher values will increase agressiveness, lower values
743 min(3% of current process size, user_reserve_kbytes) of free memory.
744 This is intended to prevent a user from starting a single memory hogging
750 all free memory with a single process, minus admin_reserve_kbytes.
752 "fork: Cannot allocate memory".
754 Changing this takes effect whenever an application requests memory.
762 the memory which is used for caching of directory and inode objects.
768 never reclaim dentries and inodes due to memory pressure and this can easily
769 lead to out-of-memory conditions. Increasing vfs_cache_pressure beyond 100
782 reclaim memory when a zone runs out of memory. If it is set to zero then no
799 memory would cause a measurable performance reduction.  The page allocator
807 since it cannot use all of system memory to buffer the outgoing writes
808 anymore but it preserve the memory on other nodes so that the performance
812 node unless explicitly overridden by memory policies or cpuset