From: Masanari Iida <standby24x7@gmail.com>
To: linux-kernel@vger.kernel.org, mhocko@suse.com,
ebiederm@xmission.com, akpm@linux-foundation.org,
stable@vger.kernel.org, corbet@lwn.net,
linux-doc@vger.kernel.org, mingo@redhat.com
Cc: Masanari Iida <standby24x7@gmail.com>
Subject: [PATCH 1/2] docs: admin-guide: Fix min value of threads-max in kernel.rst
Date: Fri, 1 Nov 2019 13:04:37 +0900 [thread overview]
Message-ID: <20191101040438.6029-1-standby24x7@gmail.com> (raw)
Since following patch was merged 5.4-rc3, minimum value for
threads-max changed to 1.
kernel/sysctl.c: do not override max_threads provided by userspace
b0f53dbc4bc4c371f38b14c391095a3bb8a0bb40
Signed-off-by: Masanari Iida <standby24x7@gmail.com>
---
Documentation/admin-guide/sysctl/kernel.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
index 032c7cd3cede..38e0f10d7d9f 100644
--- a/Documentation/admin-guide/sysctl/kernel.rst
+++ b/Documentation/admin-guide/sysctl/kernel.rst
@@ -1101,7 +1101,7 @@ During initialization the kernel sets this value such that even if the
maximum number of threads is created, the thread structures occupy only
a part (1/8th) of the available RAM pages.
-The minimum value that can be written to threads-max is 20.
+The minimum value that can be written to threads-max is 1.
The maximum value that can be written to threads-max is given by the
constant FUTEX_TID_MASK (0x3fffffff).
--
2.24.0.rc1
next reply other threads:[~2019-11-01 4:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 4:04 Masanari Iida [this message]
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
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=20191101040438.6029-1-standby24x7@gmail.com \
--to=standby24x7@gmail.com \
--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=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).