Lines Matching refs:this
12 The files in this directory can be used to tune the operation
75 Systems running under overcommit 'never' should increase this to account
84 On x86_64 this is about 8MB.
88 On x86_64 this is about 128MB.
90 Changing this takes effect whenever an application requests memory.
153 value lower than this limit will be ignored and the old configuration will be
162 of a second. Data which has been dirty in-memory for longer than this
183 Setting this to zero disables periodic writeback altogether.
189 Writing to this will cause the kernel to drop clean caches, as well as
201 To increase the number of objects freed by this operation, the user may run
210 Use of this file can cause performance problems. Since it discards cached
212 dropped objects, especially if they were under heavy use. Because of this,
215 You may see informational messages in your kernel log when this file is
244 so this parameter has no effect if used without kernelcore=.
249 of the value of this parameter.
250 IOW, this parameter affects only non-migratable hugepages.
253 this parameter is that users can make hugepage pool more extensible by
273 controlled by this knob are discussed in Documentation/laptops/laptop-mode.txt.
279 If non-zero, this sysctl disables the new 32-bit mmap layout - the kernel
291 And on large highmem machines this lack of reclaimable lowmem memory
310 The lowmem_reserve_ratio is an array. You can see them by reading this file.
315 Note: # of this elements is one fewer than number of zones. Because the highest
321 Each zone has an array of protection pages like this.
338 These protections are added to score to judge whether this zone should be used
341 In this example, if normal pages (index=2) are required to this DMA zone and
342 watermark[WMARK_HIGH] is used for watermark, the kernel judges this zone should
344 (4 + 2004 = 2008). If this protection value is 0, this zone would be used for
397 as soon as the corruption is detected. Note this is not supported
405 handle this if they want to.
410 Applications can override this setting individually with the PR_MCE_KILL prctl
427 of kilobytes free. The VM uses this number to compute a
433 allocations; if you set this to lower than 1024KB, your system will
436 Setting this too high will OOM your machine instantly.
446 than this percentage of pages in a zone are reclaimable slab pages.
463 only occur if more than this percentage of pages are in a state that
481 default this value is set to 0 and no protections will be enforced by the
482 security module. Setting this value to something like 64k will allow the
563 this is causing problems for your system/application.
576 If this is set to zero, this information is suppressed. On very
582 If this is set to non-zero, this information is shown whenever the
594 If this is set to zero, the OOM killer will scan through the entire
599 If this is set to non-zero, the OOM killer simply kills the task that
613 permitted to exceed swap plus this amount of physical RAM. See below.
625 When this flag is 0, the kernel attempts to estimate the amount
628 When this flag is 1, the kernel pretends there is always enough
631 When this flag is 2, the kernel uses a "never overcommit"
633 Note that user_reserve_kbytes affects this policy.
649 space is not permitted to exceed swap plus this percentage
667 small benefits in tuning this to a different value if your workload is
680 If this is set to 0, the kernel will kill some rogue process,
684 If this is set to 1, the kernel panics when out-of-memory happens.
687 may be killed by oom-killer. No panic occurs in this case.
691 If this is set to 2, the kernel panics compulsorily even on the
706 are allocated for each per cpu page list. The min value for this is 8. It
715 The initial value is zero. Kernel does not use this value at boot time to set
716 the high water marks for each per cpu page list. If the user writes '0' to this
717 sysctl, it will revert to this default behavior.
749 If this is reduced to zero, then the user will be allowed to allocate
754 Changing this takes effect whenever an application requests memory.
768 never reclaim dentries and inodes due to memory pressure and this can easily