linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: vbendel@redhat.com
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org, trivial@kernel.org,
	Jozef Bacik <jobacik@redhat.com>
Subject: Re: [PATCH] docs: mm: fix vm overcommit documentation for OVERCOMMIT_GUESS
Date: Mon, 29 Aug 2022 16:44:51 +0300	[thread overview]
Message-ID: <YwzC01N62rtDvzQV@kernel.org> (raw)
In-Reply-To: <20220829124638.63748-1-vbendel@redhat.com>

On Mon, Aug 29, 2022 at 02:46:38PM +0200, vbendel@redhat.com wrote:
> From: Vratislav Bendel <vbendel@redhat.com>
> 
> Commit 8c7829b04c52 "mm: fix false-positive OVERCOMMIT_GUESS failures"
> changed the behavior of the default OVERCOMMIT_GUESS setting.
> Reflect the change also in the Documentation, namely files:
>     Documentation/admin-guide/sysctl/vm.rst
>     Documentation/mm/overcommit-accounting.rst
> 
> Reported-by: Jozef Bacik <jobacik@redhat.com>
> Signed-off-by: Vratislav Bendel <vbendel@redhat.com>

Acked-by: Mike Rapoport <rppt@linux.ibm.com>

> ---
>  Documentation/admin-guide/sysctl/vm.rst    | 4 ++--
>  Documentation/mm/overcommit-accounting.rst | 3 +--
>  2 files changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/admin-guide/sysctl/vm.rst b/Documentation/admin-guide/sysctl/vm.rst
> index 9b833e439f09..351443427360 100644
> --- a/Documentation/admin-guide/sysctl/vm.rst
> +++ b/Documentation/admin-guide/sysctl/vm.rst
> @@ -742,8 +742,8 @@ overcommit_memory
>  
>  This value contains a flag that enables memory overcommitment.
>  
> -When this flag is 0, the kernel attempts to estimate the amount
> -of free memory left when userspace requests more memory.
> +When this flag is 0, the kernel compares the userspace memory request
> +size against total memory plus swap and rejects obvious overcommits.
>  
>  When this flag is 1, the kernel pretends there is always enough
>  memory until it actually runs out.
> diff --git a/Documentation/mm/overcommit-accounting.rst b/Documentation/mm/overcommit-accounting.rst
> index a4895d6fc1c2..e2263477f6d5 100644
> --- a/Documentation/mm/overcommit-accounting.rst
> +++ b/Documentation/mm/overcommit-accounting.rst
> @@ -8,8 +8,7 @@ The Linux kernel supports the following overcommit handling modes
>  	Heuristic overcommit handling. Obvious overcommits of address
>  	space are refused. Used for a typical system. It ensures a
>  	seriously wild allocation fails while allowing overcommit to
> -	reduce swap usage.  root is allowed to allocate slightly more
> -	memory in this mode. This is the default.
> +	reduce swap usage. This is the default.
>  
>  1
>  	Always overcommit. Appropriate for some scientific
> -- 
> 2.26.3
> 

-- 
Sincerely yours,
Mike.

  reply	other threads:[~2022-08-29 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 12:46 [PATCH] docs: mm: fix vm overcommit documentation for OVERCOMMIT_GUESS vbendel
2022-08-29 13:44 ` Mike Rapoport [this message]
     [not found]   ` <CAHrQN1yOTTMz=RR0rJxr9aFVmTPgYyrabPzNH00Z-fToorrPjQ@mail.gmail.com>
2023-10-10 19:09     ` Jonathan Corbet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YwzC01N62rtDvzQV@kernel.org \
    --to=rppt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=jobacik@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@kernel.org \
    --cc=vbendel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).