[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180510125211.12583-1-dima@arista.com>
Date: Thu, 10 May 2018 13:52:09 +0100
From: Dmitry Safonov <dima@...sta.com>
To: linux-kernel@...r.kernel.org
Cc: 0x7f454c46@...il.com, Dmitry Safonov <dima@...sta.com>,
Arnd Bergmann <arnd@...db.de>, Theodore Ts'o <tytso@....edu>,
David Airlie <airlied@...ux.ie>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jani Nikula <jani.nikula@...ux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
intel-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org
Subject: [PATCH 0/2] ratelimit: Do not lose messages under limit
There are two issues with ratelimiting as far a I can see:
1. Messages may be lost even if their amount fit burst limit;
2. "suppressed" message may not be printed if there is no call to
___ratelimit() after interval ends.
I address (1) issue in the second patch.
While the (2) issue will require adding timers to print "suppressed"
message and care if ratelimit is on stack and no more exists. Which
looks too much at this point.
Dmitry Safonov (2):
random: Omit double-printing ratelimit messages
lib/ratelimit: Lockless ratelimiting
drivers/char/random.c | 22 +++++++--------
drivers/gpu/drm/i915/i915_perf.c | 4 +--
include/linux/ratelimit.h | 34 ++++++++++++++---------
lib/ratelimit.c | 59 +++++++++++++++++++---------------------
4 files changed, 61 insertions(+), 58 deletions(-)
--
2.13.6
Powered by blists - more mailing lists