From: Michal Hocko <mhocko@kernel.org>
To: Masanari Iida <standby24x7@gmail.com>
Cc: linux-kernel@vger.kernel.org, ebiederm@xmission.com,
akpm@linux-foundation.org, stable@vger.kernel.org,
corbet@lwn.net, linux-doc@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCH 2/2] docs: admin-guide: Remove threads-max auto-tuning
Date: Tue, 5 Nov 2019 07:30:29 +0100 [thread overview]
Message-ID: <20191105063029.GD22672@dhcp22.suse.cz> (raw)
In-Reply-To: <20191101040438.6029-2-standby24x7@gmail.com>
On Fri 01-11-19 13:04:38, Masanari Iida wrote:
> Since following path was merged in 5.4-rc3,
> auto-tuning feature in threads-max was not exist any more.
> Fix the admin-guide document as is.
>
> kernel/sysctl.c: do not override max_threads provided by userspace
> b0f53dbc4bc4c371f38b14c391095a3bb8a0bb40
>
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
Acked-by: Michal Hocko <mhocko@suse.com>
> ---
> Documentation/admin-guide/sysctl/kernel.rst | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
> index 38e0f10d7d9f..9035adbdff58 100644
> --- a/Documentation/admin-guide/sysctl/kernel.rst
> +++ b/Documentation/admin-guide/sysctl/kernel.rst
> @@ -1109,10 +1109,6 @@ constant FUTEX_TID_MASK (0x3fffffff).
> If a value outside of this range is written to threads-max an error
> EINVAL occurs.
>
> -The value written is checked against the available RAM pages. If the
> -thread structures would occupy too much (more than 1/8th) of the
> -available RAM pages threads-max is reduced accordingly.
> -
>
> unknown_nmi_panic:
> ==================
> --
> 2.24.0.rc1
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-11-05 6:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 4:04 [PATCH 1/2] docs: admin-guide: Fix min value of threads-max in kernel.rst Masanari Iida
2019-11-01 4:04 ` [PATCH 2/2] docs: admin-guide: Remove threads-max auto-tuning Masanari Iida
2019-11-05 6:30 ` Michal Hocko [this message]
2019-11-05 6:30 ` [PATCH 1/2] docs: admin-guide: Fix min value of threads-max in kernel.rst Michal Hocko
2019-11-07 19:43 ` 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=20191105063029.GD22672@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=ebiederm@xmission.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stable@vger.kernel.org \
--cc=standby24x7@gmail.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).