From dc10ec987903c2f6ee74a04da278a1f830fd9f3e Mon Sep 17 00:00:00 2001 From: Anssi Hannula Date: Sat, 11 Dec 2021 21:41:59 +0200 Subject: docs/vm: clarify overcommit amount sysctl behavior Documentation/vm/overcommit-accounting.rst says that the overcommit amount can be set via vm.overcommit_ratio and vm.overcommit_kbytes. Add a clarification that those only take effect in overcommit handling mode 2 ("Don't overcommit"), i.e. they do not act as an "additional" limit that is always enforced. Signed-off-by: Anssi Hannula Reviewed-by: David Hildenbrand Link: https://lore.kernel.org/r/20211211194159.3137362-1-anssi.hannula@iki.fi Signed-off-by: Jonathan Corbet --- Documentation/vm/overcommit-accounting.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'Documentation/vm') diff --git a/Documentation/vm/overcommit-accounting.rst b/Documentation/vm/overcommit-accounting.rst index 0dd54bbe4afa..1addb0c374a4 100644 --- a/Documentation/vm/overcommit-accounting.rst +++ b/Documentation/vm/overcommit-accounting.rst @@ -34,7 +34,8 @@ The Linux kernel supports the following overcommit handling modes The overcommit policy is set via the sysctl ``vm.overcommit_memory``. The overcommit amount can be set via ``vm.overcommit_ratio`` (percentage) -or ``vm.overcommit_kbytes`` (absolute value). +or ``vm.overcommit_kbytes`` (absolute value). These only have an effect +when ``vm.overcommit_memory`` is set to 2. The current overcommit limit and amount committed are viewable in ``/proc/meminfo`` as CommitLimit and Committed_AS respectively. -- cgit v1.2.3-59-g8ed1b