[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191101040438.6029-2-standby24x7@gmail.com>
Date: Fri, 1 Nov 2019 13:04:38 +0900
From: Masanari Iida <standby24x7@...il.com>
To: linux-kernel@...r.kernel.org, mhocko@...e.com,
ebiederm@...ssion.com, akpm@...ux-foundation.org,
stable@...r.kernel.org, corbet@....net, linux-doc@...r.kernel.org,
mingo@...hat.com
Cc: Masanari Iida <standby24x7@...il.com>
Subject: [PATCH 2/2] docs: admin-guide: Remove threads-max auto-tuning
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@...il.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
Powered by blists - more mailing lists