linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Fengfei Xi <xi.fengfei@h3c.com>
Cc: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] docs: admin-guide: Fix default value of max_map_count in sysctl/vm.rst
Date: Mon, 21 Dec 2020 09:59:23 -0700	[thread overview]
Message-ID: <20201221095923.67dacea4@lwn.net> (raw)
In-Reply-To: <20201210082134.36957-1-xi.fengfei@h3c.com>

On Thu, 10 Dec 2020 16:21:34 +0800
Fengfei Xi <xi.fengfei@h3c.com> wrote:

> Since the default value of sysctl_max_map_count is defined as
> DEFAULT_MAX_MAP_COUNT from mm/util.c
> 
>     int sysctl_max_map_count __read_mostly = DEFAULT_MAX_MAP_COUNT;
> 
> DEFAULT_MAX_MAP_COUNT is defined as 65530 (65535-5) in include/linux/mm.h
> 
>     #define MAPCOUNT_ELF_CORE_MARGIN        (5)
>     #define DEFAULT_MAX_MAP_COUNT   (USHRT_MAX - MAPCOUNT_ELF_CORE_MARGIN)
> 
> Signed-off-by: Fengfei Xi <xi.fengfei@h3c.com>
> ---
>  Documentation/admin-guide/sysctl/vm.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/admin-guide/sysctl/vm.rst b/Documentation/admin-guide/sysctl/vm.rst
> index f455fa00c..834c3fc74 100644
> --- a/Documentation/admin-guide/sysctl/vm.rst
> +++ b/Documentation/admin-guide/sysctl/vm.rst
> @@ -428,7 +428,7 @@ While most applications need less than a thousand maps, certain
>  programs, particularly malloc debuggers, may consume lots of them,
>  e.g., up to one or two maps per allocation.
>  
> -The default value is 65536.
> +The default value is 65530.

Applied, thanks.

jon

      reply	other threads:[~2020-12-21 17:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10  8:21 [PATCH] docs: admin-guide: Fix default value of max_map_count in sysctl/vm.rst Fengfei Xi
2020-12-21 16:59 ` Jonathan Corbet [this message]

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=20201221095923.67dacea4@lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xi.fengfei@h3c.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).