[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080506122423.051b4254.akpm@linux-foundation.org>
Date: Tue, 6 May 2008 12:24:23 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Dave Young <hidave.darkstar@...il.com>
Cc: paulmck@...ibm.com, joe@...ches.com, davem@...emloft.net,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm][v2] ratelimit rewrite
On Tue, 6 May 2008 10:25:58 +0800
Dave Young <hidave.darkstar@...il.com> wrote:
> [Fixed a macro error found by davem, added more changes description.]
>
> ---
> All ratelimit user use same jiffies and burst params, so some messages
> (callbacks) will be lost.
>
> For example:
> a call printk_ratelimit(5 * HZ, 1)
> b call printk_ratelimit(5 * HZ, 1) before the 5*HZ timeout of a, then b will
> will be supressed.
>
> Changes:
> 1. rewrite __ratelimit, and use a ratelimit_state as parameter.
> Thanks for hints from andrew.
> 2. change WARN_ON_SECS to WARN_ON_RATELIMIT, update rcupreempt.h
> 3. remove __printk_ratelimit
> 4. use __ratelimit in net_ratelimit
I rebased this on top of mainline+linux-next+mm-stuff. I'll drop
add-warn_on_secs-macro.patch and use-warn_on_secs-in-rcupreempth.patch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists