From: Jim Keniston <jkenisto@us.ibm.com>
To: Rask Ingemann Lambertsen <rask@sygehus.dk>
Cc: LKML <linux-kernel@vger.kernel.org>, netdev <netdev@oss.sgi.com>,
Jeff Garzik <jgarzik@pobox.com>, Andrew Morton <akpm@osdl.org>,
"Feldman, Scott" <scott.feldman@intel.com>,
Larry Kessler <kessler@us.ibm.com>
Subject: Re: [PATCH 2.6.1] Net device error logging
Date: Tue, 20 Jan 2004 15:06:21 -0800 [thread overview]
Message-ID: <400DB46D.67E852D9@us.ibm.com> (raw)
In-Reply-To: 20040120195122.A1087@sygehus.dk
Rask Ingemann Lambertsen wrote:
>
> On Mon, Jan 19, 2004 at 12:25:34PM -0800, Jim Keniston wrote:
> > The enclosed patch implements the netdev_* error-logging macros for
> > network drivers. These macros have been discussed at length on the
> > linux-kernel and linux-netdev lists. All issues that reviewers have
> > raised were addressed previously. This is just an update for v2.6.1.
>
> How about a message rate limit?
>
> --
> Regards,
> Rask Ingemann Lambertsen
Thanks. We considered adding a ratelimit flag to the netdev_printk arg
list. It was pointed out that
(1) rate-limiting is necessary for a relatively small subset of messages;
and
(2) the NETIF_MSG_* flags are already designed to be used in order of
increasing verbosity. If the user selects the more verbose class of
messages, then rate-limiting may not be appropriate.
I concluded that ratelimit() should continue to be used on a case-by-case
basis, and not folded into netdev_printk.
Jim Keniston
prev parent reply other threads:[~2004-01-20 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 20:25 [PATCH 2.6.1] Net device error logging Jim Keniston
2004-01-20 2:46 ` Andrew Morton
2004-01-20 23:19 ` Jim Keniston
2004-01-20 18:51 ` Rask Ingemann Lambertsen
2004-01-20 23:06 ` Jim Keniston [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=400DB46D.67E852D9@us.ibm.com \
--to=jkenisto@us.ibm.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=kessler@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=rask@sygehus.dk \
--cc=scott.feldman@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).