From: Jonathan Corbet <corbet@lwn.net>
To: Eric Curtin <ericcurtin17@gmail.com>
Cc: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
linux-doc@vger.kernel.org (open list:DOCUMENTATION),
linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH] Update Documentation/admin-guide/sysctl/fs.rst
Date: Thu, 28 Jan 2021 15:45:37 -0700 [thread overview]
Message-ID: <20210128154537.2ed50d06@lwn.net> (raw)
In-Reply-To: <20210120132648.19046-1-ericcurtin17@gmail.com>
On Wed, 20 Jan 2021 13:26:47 +0000
Eric Curtin <ericcurtin17@gmail.com> wrote:
> max_user_watches for epoll should say 1/25, rather than 1/32
>
> Signed-off-by: Eric Curtin <ericcurtin17@gmail.com>
> ---
> Documentation/admin-guide/sysctl/fs.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/admin-guide/sysctl/fs.rst b/Documentation/admin-guide/sysctl/fs.rst
> index f48277a0a850..2a501c9ddc55 100644
> --- a/Documentation/admin-guide/sysctl/fs.rst
> +++ b/Documentation/admin-guide/sysctl/fs.rst
> @@ -380,5 +380,5 @@ This configuration option sets the maximum number of "watches" that are
> allowed for each user.
> Each "watch" costs roughly 90 bytes on a 32bit kernel, and roughly 160 bytes
> on a 64bit one.
> -The current default value for max_user_watches is the 1/32 of the available
> -low memory, divided for the "watch" cost in bytes.
> +The current default value for max_user_watches is the 1/25 (4%) of the
> +available low memory, divided for the "watch" cost in bytes.
That does appear to be the way of it...patch applied, thanks.
jon
prev parent reply other threads:[~2021-01-28 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 13:26 [PATCH] Update Documentation/admin-guide/sysctl/fs.rst Eric Curtin
2021-01-28 22:45 ` 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=20210128154537.2ed50d06@lwn.net \
--to=corbet@lwn.net \
--cc=ericcurtin17@gmail.com \
--cc=grandmaster@al2klimov.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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