linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] docs: admin-guide: fix printk_ratelimit explanation
@ 2019-10-02 11:46 Oleksandr Natalenko
  2019-10-09 11:22 ` Oleksandr Natalenko
  2019-10-10 17:35 ` Jonathan Corbet
  0 siblings, 2 replies; 3+ messages in thread
From: Oleksandr Natalenko @ 2019-10-02 11:46 UTC (permalink / raw)
  To: linux-kernel
  Cc: linux-doc, Jonathan Corbet, Mauro Carvalho Chehab, Vasily Gorbik,
	Ingo Molnar, Heiko Carstens, Thorsten Leemhuis, Quentin Perret

The printk_ratelimit value accepts seconds, not jiffies (though it is
converted into jiffies internally). Update documentation to reflect
this.

Also, remove the statement about allowing 1 message in 5 seconds since
bursts up to 10 messages are allowed by default.

Finally, while we are here, mention default value for
printk_ratelimit_burst too.

Signed-off-by: Oleksandr Natalenko <oleksandr@redhat.com>
---
 Documentation/admin-guide/sysctl/kernel.rst | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
index 032c7cd3cede..6e0da29e55f1 100644
--- a/Documentation/admin-guide/sysctl/kernel.rst
+++ b/Documentation/admin-guide/sysctl/kernel.rst
@@ -831,8 +831,8 @@ printk_ratelimit:
 =================
 
 Some warning messages are rate limited. printk_ratelimit specifies
-the minimum length of time between these messages (in jiffies), by
-default we allow one every 5 seconds.
+the minimum length of time between these messages (in seconds).
+The default value is 5 seconds.
 
 A value of 0 will disable rate limiting.
 
@@ -845,6 +845,8 @@ 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.
 
+The default value is 10 messages.
+
 
 printk_devkmsg:
 ===============
-- 
2.23.0


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] docs: admin-guide: fix printk_ratelimit explanation
  2019-10-02 11:46 [PATCH] docs: admin-guide: fix printk_ratelimit explanation Oleksandr Natalenko
@ 2019-10-09 11:22 ` Oleksandr Natalenko
  2019-10-10 17:35 ` Jonathan Corbet
  1 sibling, 0 replies; 3+ messages in thread
From: Oleksandr Natalenko @ 2019-10-09 11:22 UTC (permalink / raw)
  To: linux-kernel
  Cc: linux-doc, Jonathan Corbet, Mauro Carvalho Chehab, Vasily Gorbik,
	Ingo Molnar, Heiko Carstens, Thorsten Leemhuis, Quentin Perret

Hi.

On Wed, Oct 02, 2019 at 01:46:10PM +0200, Oleksandr Natalenko wrote:
> The printk_ratelimit value accepts seconds, not jiffies (though it is
> converted into jiffies internally). Update documentation to reflect
> this.
> 
> Also, remove the statement about allowing 1 message in 5 seconds since
> bursts up to 10 messages are allowed by default.
> 
> Finally, while we are here, mention default value for
> printk_ratelimit_burst too.
> 
> Signed-off-by: Oleksandr Natalenko <oleksandr@redhat.com>
> ---
>  Documentation/admin-guide/sysctl/kernel.rst | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
> index 032c7cd3cede..6e0da29e55f1 100644
> --- a/Documentation/admin-guide/sysctl/kernel.rst
> +++ b/Documentation/admin-guide/sysctl/kernel.rst
> @@ -831,8 +831,8 @@ printk_ratelimit:
>  =================
>  
>  Some warning messages are rate limited. printk_ratelimit specifies
> -the minimum length of time between these messages (in jiffies), by
> -default we allow one every 5 seconds.
> +the minimum length of time between these messages (in seconds).
> +The default value is 5 seconds.
>  
>  A value of 0 will disable rate limiting.
>  
> @@ -845,6 +845,8 @@ 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.
>  
> +The default value is 10 messages.
> +
>  
>  printk_devkmsg:
>  ===============
> -- 
> 2.23.0
> 

This is a gentle ping. Please review.

Thanks.

-- 
  Best regards,
    Oleksandr Natalenko (post-factum)
    Senior Software Maintenance Engineer


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] docs: admin-guide: fix printk_ratelimit explanation
  2019-10-02 11:46 [PATCH] docs: admin-guide: fix printk_ratelimit explanation Oleksandr Natalenko
  2019-10-09 11:22 ` Oleksandr Natalenko
@ 2019-10-10 17:35 ` Jonathan Corbet
  1 sibling, 0 replies; 3+ messages in thread
From: Jonathan Corbet @ 2019-10-10 17:35 UTC (permalink / raw)
  To: Oleksandr Natalenko
  Cc: linux-kernel, linux-doc, Mauro Carvalho Chehab, Vasily Gorbik,
	Ingo Molnar, Heiko Carstens, Thorsten Leemhuis, Quentin Perret

On Wed,  2 Oct 2019 13:46:10 +0200
Oleksandr Natalenko <oleksandr@redhat.com> wrote:

> The printk_ratelimit value accepts seconds, not jiffies (though it is
> converted into jiffies internally). Update documentation to reflect
> this.
> 
> Also, remove the statement about allowing 1 message in 5 seconds since
> bursts up to 10 messages are allowed by default.
> 
> Finally, while we are here, mention default value for
> printk_ratelimit_burst too.
> 
> Signed-off-by: Oleksandr Natalenko <oleksandr@redhat.com>

This seems good.  Applied, thanks.

jon

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2019-10-10 17:35 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-02 11:46 [PATCH] docs: admin-guide: fix printk_ratelimit explanation Oleksandr Natalenko
2019-10-09 11:22 ` Oleksandr Natalenko
2019-10-10 17:35 ` Jonathan Corbet

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).