summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorBrian Masney <bmasney@redhat.com>2026-05-28 16:45:10 +0300
committerAndrew Morton <akpm@linux-foundation.org>2026-06-05 00:45:08 +0300
commita195cf013e98b02d3c129e2cccd7efa98aabf546 (patch)
treea6358d2510f07b8635b8aa632f59de1663705d62 /include
parent8f42b751e7d7f73dbb2b59281cef891bfb7ae40c (diff)
downloadlinux-a195cf013e98b02d3c129e2cccd7efa98aabf546.tar.xz
docs: mm: clarify that user_reserve_kbytes has no effect when overcommit_memory is set to 0 or 1
Looking at __vm_enough_memory() in mm/util.c, user_reserve_kbytes has no effect when overcommit_memory is set to 0 or 1. The documentation for overcommit_memory already references user_reserve_kbytes when the flag is set to 2. Let's go ahead and add a clarification to user_reserve_kbytes in vm.rst that it has no effect when overcommit_memory is set to 0 or 1. Link: https://lore.kernel.org/20260528-mm-clarify-docs-v1-1-aa88e83b4bfd@redhat.com Signed-off-by: Brian Masney <bmasney@redhat.com> Cc: David Hildenbrand <david@kernel.org> Cc: Jonathan Corbet <corbet@lwn.net> Cc: Liam R. Howlett <liam@infradead.org> Cc: Lorenzo Stoakes <ljs@kernel.org> Cc: Shuah Khan <skhan@linuxfoundation.org> Cc: Vlastimil Babka <vbabka@kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions