From: Janice M Girouard <janiceg@us.ibm.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "David S. Miller" <davem@redhat.com>,
shemminger@osdl.org, Valdis.Kletnieks@vt.edu,
Janice Girouard <girouard@us.ibm.com>,
Daniel Stekloff <stekloff@us.ibm.com>,
Larry Kessler <lkessler@us.ibm.com>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com, niv@us.ibm.com
Subject: Re: patch for common networking error messages
Date: Tue, 17 Jun 2003 14:46:56 -0500 [thread overview]
Message-ID: <3EEF7030.6030303@us.ibm.com> (raw)
In-Reply-To: 3EEF6A9D.6050303@pobox.com
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
Jeff Garzik wrote:
Do you want to individually send 4000 - 16000 (or more) TX stop /
start events per second to userspace? :) At some point Heisenburg
defeats low latency :)
How about looking at 1000 byte packet transmit example. A gigabit
adapter would send 125,000 packets per second. I'm thinking that most
of the time, you will have enough available buffers in the adapter that
you don't start to see the adapter buffers completely fill up. Are you
saying that 3.2% - 12.8% of the time in this case you're disabling the
tcp/ip stack because the transmit buffers on your card are completely
full? Perhaps with zero copy enabled, but the tcp/ip cpu load alone
will throttle your ability to fill the adapter buffers up.
What does your own experience indicate for gigabit adapter cards?
I could see the buffers backing up for 10/100 cards. So that case
favors your point. I'm still thinking that it's a sign someone should
be buying a 2nd card and ramping up their network capability. But I can
see your point.
next prev parent reply other threads:[~2003-06-17 19:46 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 2:12 patch for common networking error messages 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 [this message]
2003-06-17 19:50 ` David S. Miller
2003-06-17 20:24 ` Janice M Girouard
2003-06-17 20:27 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2003-06-17 20:57 Janice Girouard
2003-06-17 21:14 ` David S. Miller
2003-06-17 20:40 Janice Girouard
2003-06-17 20:42 ` David S. Miller
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-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-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 20:30 Janice M Girouard
2003-06-16 20:38 ` David S. Miller
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
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=3EEF7030.6030303@us.ibm.com \
--to=janiceg@us.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=davem@redhat.com \
--cc=girouard@us.ibm.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkessler@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=niv@us.ibm.com \
--cc=shemminger@osdl.org \
--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 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).