Skip to contentSkip to conversation

docs: kernel: Clarify printk_ratelimit_burst reset behavior

PATCH Applied Breno Leitao 3 participants 3 messages Jul 14, 2025 – Jul 17, 2025 Documentation

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 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.

---
 Documentation/admin-guide/sysctl/kernel.rst | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
Documentation/admin-guide/sysctl/kernel.rst +2 -1
index a43b78b4b6464..6f8d3935147da 100644
@@ -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,

Signature · 1 line
Breno Leitao <[email protected]>
Reviewed-by on v1 1/1
#1 lore raw
Quoted 6 lines · Breno Leitao

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.

Quoted 27 lines
---
 Documentation/admin-guide/sysctl/kernel.rst | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
Documentation/admin-guide/sysctl/kernel.rst +2 -2
index a43b78b4b6464..6f8d3935147da 100644
@@ -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,

Signature · 1 line
Breno Leitao <[email protected]>
maintainer Applied
#2 lore raw
In reply to Breno Leitao
Quoted 15 lines · Breno Leitao

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.

---
 Documentation/admin-guide/sysctl/kernel.rst | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
Documentation/admin-guide/sysctl/kernel.rst +0 -0
index a43b78b4b6464..6f8d3935147da 100644

Documentation/admin-guide/sysctl/kernel.rst printk_ratelimit_burst · line 1104

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

Applied, thanks.

jon