Skip to contentSkip to conversation

Update Documentation/admin-guide/sysctl/fs.rst

PATCH In review Eric Curtin 2 participants 2 messages Jan 20, 2021 – Jan 28, 2021 Documentation

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Update Documentation/admin-guide/sysctl/fs.rst

max_user_watches for epoll should say 1/25, rather than 1/32

---
 Documentation/admin-guide/sysctl/fs.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/admin-guide/sysctl/fs.rst +2 -2
index f48277a0a850..2a501c9ddc55 100644
@@ -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.
Signature · 1 line
2.25.1
maintainer
#1 lore raw
Quoted 12 lines · On Wed, 20 Jan 2021 13:26:47 +0000 Eric Curtin <[email protected]> wrote:

max_user_watches for epoll should say 1/25, rather than 1/32

---
 Documentation/admin-guide/sysctl/fs.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/admin-guide/sysctl/fs.rst +0 -0
index f48277a0a850..2a501c9ddc55 100644

Documentation/admin-guide/sysctl/fs.rst This configuration option sets the maximum number of "watches" that are · line 384

Quoted 7 lines
Documentation/admin-guide/sysctl/fs.rst +2 -2
@@ -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