Lines Matching +full:message +full:- +full:handling +full:- +full:unit

13 ------------------------------------------------------------------------------
27 - admin_reserve_kbytes
28 - block_dump
29 - compact_memory
30 - compact_unevictable_allowed
31 - dirty_background_bytes
32 - dirty_background_ratio
33 - dirty_bytes
34 - dirty_expire_centisecs
35 - dirty_ratio
36 - dirtytime_expire_seconds
37 - dirty_writeback_centisecs
38 - drop_caches
39 - extfrag_threshold
40 - extra_free_kbytes
41 - hugetlb_shm_group
42 - laptop_mode
43 - legacy_va_layout
44 - lowmem_reserve_ratio
45 - max_map_count
46 - memory_failure_early_kill
47 - memory_failure_recovery
48 - min_free_kbytes
49 - min_slab_ratio
50 - min_unmapped_ratio
51 - mmap_min_addr
52 - mmap_rnd_bits
53 - mmap_rnd_compat_bits
54 - nr_hugepages
55 - nr_hugepages_mempolicy
56 - nr_overcommit_hugepages
57 - nr_trim_pages         (only if CONFIG_MMU=n)
58 - numa_zonelist_order
59 - oom_dump_tasks
60 - oom_kill_allocating_task
61 - overcommit_kbytes
62 - overcommit_memory
63 - overcommit_ratio
64 - page-cluster
65 - panic_on_oom
66 - percpu_pagelist_fraction
67 - stat_interval
68 - stat_refresh
69 - numa_stat
70 - swappiness
71 - unprivileged_userfaultfd
72 - user_reserve_kbytes
73 - vfs_cache_pressure
74 - watermark_boost_factor
75 - watermark_scale_factor
76 - zone_reclaim_mode
112 information on block I/O debugging is in Documentation/admin-guide/laptops/laptop-mode.rst.
178 of a second.  Data which has been dirty in-memory for longer than this
233 This is a non-destructive operation and will not free any dirty objects.
261 reclaim to satisfy a high-order allocation. The extfrag/extfrag_index file in
264 of memory, values towards 1000 imply failures are due to fragmentation and -1
285 storage more effectively. Note this also comes with a risk of pre-mature
300 (causing in-kernel memory allocations) with a maximum total message burst
317 controlled by this knob are discussed in Documentation/admin-guide/laptops/laptop-mode.rst.
323 If non-zero, this sysctl disables the new 32-bit mmap layout - the kernel
361 in /proc/zoneinfo like followings. (This is an example of x86-64 box).
391     zone[i]->protection[j]
411 The minimum value is 1 (1/1 -> 100%). The value less than 1 completely
419 may have. Memory map areas are used as a side-effect of calling
453 check handling and depends on the hardware capabilities.
512 against all file-backed unmapped pages including swapcache pages and tmpfs
564 See Documentation/admin-guide/mm/hugetlbpage.rst
570 Change the size of the hugepage pool at run-time on a specific
573 See Documentation/admin-guide/mm/hugetlbpage.rst
582 See Documentation/admin-guide/mm/hugetlbpage.rst
590 This value adjusts the excess page trimming behaviour of power-of-2 aligned
599 See Documentation/nommu-mmap.txt for more information.
613 In non-NUMA case, a zonelist for GFP_KERNEL is ordered as following.
614 ZONE_NORMAL -> ZONE_DMA
621   (A) Node(0) ZONE_NORMAL -> Node(0) ZONE_DMA -> Node(1) ZONE_NORMAL
622   (B) Node(0) ZONE_NORMAL -> Node(1) ZONE_NORMAL -> Node(0) ZONE_DMA.
626 out-of-memory(OOM) of ZONE_DMA because ZONE_DMA is tend to be small.
641 On 32-bit, the Normal zone needs to be preserved for allocations accessible
644 On 64-bit, devices that require DMA32/DMA are relatively rare, so "node"
654 Enables a system-wide task dump (excluding kernel threads) to be produced
655 when the kernel performs an OOM-killing and includes such information as
667 If this is set to non-zero, this information is shown whenever the
668 OOM killer actually kills a memory-hogging task.
676 This enables or disables killing the OOM-triggering task in
677 out-of-memory situations.
681 selects a rogue memory-hogging task that frees up a large amount of
684 If this is set to non-zero, the OOM killer simply kills the task that
685 triggered the out-of-memory condition.  This avoids the expensive
721 programs that malloc() huge amounts of memory "just-in-case"
726 See Documentation/vm/overcommit-accounting.rst and
738 page-cluster
741 page-cluster controls the number of pages up to which consecutive pages
745 but consecutive on swap space - that means they were swapped out together.
747 It is a logarithmic value - setting it to zero means "1 page", setting
753 swap-intensive.
763 This enables or disables panic on out-of-memory feature.
769 If this is set to 1, the kernel panics when out-of-memory happens.
772 may be killed by oom-killer. No panic occurs in this case.
777 above-mentioned. Even oom happens under memory cgroup, the whole
792 This is the fraction of pages at most (high mark pcp->high) in each zone that
800 set to pcp->high/4.  The upper limit of batch is (PAGE_SHIFT * 8)
817 Any read or write (by root only) flushes all the per-cpu vm statistics
821 As a side-effect, it also checks for negative totals (elsewhere reported
850 initiate swap until the amount of free and file-backed pages is less
896 lead to out-of-memory conditions. Increasing vfs_cache_pressure beyond 100
912 increase the success rate of future high-order allocations such as SLUB
916 parameter, the unit is in fractions of 10,000. The default value of
922 (e.g.  2MB on 64-bit x86). A boost factor of 0 will disable the feature.
932 The unit is in fractions of 10,000. The default value of 10 means the