[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250714-docs_ratelimit-v1-1-51a6d9071f1a@debian.org>
Date: Mon, 14 Jul 2025 05:06:27 -0700
From: Breno Leitao <leitao@...ian.org>
To: Jonathan Corbet <corbet@....net>
Cc: paulmck@...nel.org, pmladek@...e.com, rostedt@...dmis.org,
john.ogness@...utronix.de, senozhatsky@...omium.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
Breno Leitao <leitao@...ian.org>
Subject: [PATCH] docs: kernel: Clarify printk_ratelimit_burst reset
behavior
Add clarification that the printk_ratelimit_burst window resets after
printk_ratelimit seconds have elapsed, allowing another burst of
messages to be sent. This helps users understand that the rate limiting
is not permanent but operates in periodic windows.
Signed-off-by: Breno Leitao <leitao@...ian.org>
---
Documentation/admin-guide/sysctl/kernel.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
index a43b78b4b6464..6f8d3935147da 100644
--- a/Documentation/admin-guide/sysctl/kernel.rst
+++ b/Documentation/admin-guide/sysctl/kernel.rst
@@ -1099,7 +1099,8 @@ printk_ratelimit_burst
While long term we enforce one message per `printk_ratelimit`_
seconds, we do allow a burst of messages to pass through.
``printk_ratelimit_burst`` specifies the number of messages we can
-send before ratelimiting kicks in.
+send before ratelimiting kicks in. After `printk_ratelimit`_ seconds
+have elapsed, another burst of messages may be sent.
The default value is 10 messages.
---
base-commit: 0907e7fb35756464aa34c35d6abb02998418164b
change-id: 20250714-docs_ratelimit-8f4a30f29908
Best regards,
--
Breno Leitao <leitao@...ian.org>
Powered by blists - more mailing lists