From: "David S. Miller" <davem@redhat.com>
To: janiceg@us.ibm.com
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
stekloff@us.ibm.com, girouard@us.ibm.com, lkessler@us.ibm.com,
kenistonj@us.ibm.com, jgarzik@pobox.com
Subject: Re: patch for common networking error messages
Date: Mon, 16 Jun 2003 13:38:41 -0700 (PDT) [thread overview]
Message-ID: <20030616.133841.35533284.davem@redhat.com> (raw)
In-Reply-To: <3EEE28DE.6040808@us.ibm.com>
From: Janice M Girouard <janiceg@us.ibm.com>
Date: Mon, 16 Jun 2003 15:30:22 -0500
EMSG_NET_LINK_UP "%s: state change: link up, %d Mbps, %s-duplex\n"
Should indicate flow control state too.
EMSG_NET_START_QUEUE "%s: performance event: (re)starting netdev queue\n"
EMSG_NET_STOP_QUEUE "%s: performance event: stopping netdev queue\n"
Oh _ABSOLUTELY NOT_, you're not printing a message
for normal events like this. Especially those that are
going to occur on highly loaded systems.
next prev parent reply other threads:[~2003-06-16 20:29 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 20:30 patch for common networking error messages Janice M Girouard
2003-06-16 20:38 ` David S. Miller [this message]
2003-06-16 20:53 ` Andi Kleen
2003-06-16 20:51 ` David S. Miller
2003-06-16 22:27 ` Andrew Morton
2003-06-17 7:09 ` Andi Kleen
2003-06-17 7:20 ` Andrew Morton
2003-06-16 20:59 ` Janice M Girouard
2003-06-16 22:48 ` Jeff Garzik
2003-06-16 22:52 ` Jeff Garzik
2003-06-16 22:13 ` Nivedita Singhvi
2003-06-16 22:13 ` David S. Miller
2003-06-16 22:50 ` Nivedita Singhvi
2003-06-16 22:57 ` David S. Miller
2003-06-16 23:02 ` Donald Becker
-- strict thread matches above, loose matches on Subject: below --
2003-06-16 22:29 Janice Girouard
2003-06-16 22:27 ` David S. Miller
2003-06-16 22:45 ` Nivedita Singhvi
2003-06-16 22:52 ` David S. Miller
2003-06-17 0:07 ` Nivedita Singhvi
2003-06-16 22:50 Janice Girouard
2003-06-16 22:55 ` David S. Miller
2003-06-21 12:36 ` Alan Cox
2003-06-21 14:27 ` Jamal Hadi
2003-06-23 0:46 ` David S. Miller
2003-06-23 11:54 ` Alan Cox
2003-06-17 0:44 Janice Girouard
2003-06-17 1:19 ` David S. Miller
2003-06-17 14:34 ` Mr. James W. Laferriere
2003-06-17 2:12 Janice Girouard
2003-06-17 4:34 ` Valdis.Kletnieks
2003-06-17 16:08 ` Stephen Hemminger
2003-06-17 16:09 ` David S. Miller
2003-06-17 18:46 ` Jeff Garzik
2003-06-17 19:06 ` Janice M Girouard
2003-06-17 19:23 ` Jeff Garzik
2003-06-17 19:46 ` Janice M Girouard
2003-06-17 19:50 ` David S. Miller
2003-06-17 20:24 ` Janice M Girouard
2003-06-17 20:27 ` David S. Miller
2003-06-17 20:40 Janice Girouard
2003-06-17 20:42 ` David S. Miller
2003-06-17 20:57 Janice Girouard
2003-06-17 21:14 ` David S. Miller
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=20030616.133841.35533284.davem@redhat.com \
--to=davem@redhat.com \
--cc=girouard@us.ibm.com \
--cc=janiceg@us.ibm.com \
--cc=jgarzik@pobox.com \
--cc=kenistonj@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkessler@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=stekloff@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.