From: Janice M Girouard <janiceg@us.ibm.com>
To: "David S. Miller" <davem@redhat.com>
Cc: jgarzik@pobox.com, shemminger@osdl.org, Valdis.Kletnieks@vt.edu,
girouard@us.ibm.com, stekloff@us.ibm.com, 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 15:24:20 -0500 [thread overview]
Message-ID: <3EEF78F4.2070604@us.ibm.com> (raw)
In-Reply-To: 20030617.125040.58438649.davem@redhat.com
From David S. Miller:
And when we have 1GHZ memory busses and 10GHz cpus tomorrow,
what does this say for 1gbit and 10gbit cards?
Such schemes are fundamentally flawed.
Bottom line.. I was asking for input, and I received it. It's valid
to say... look at the statistics. I really like the concept of driving
events through netlink, but querying statistics works.
p.s. It's been my experience that the memory system is the main
bottleneck when trying to support a heavy network load. When the 10
Gigabit card emerges, and it's here today, the memory system will be
pressed to support it, especially if you're not using zerocopy and
you're thinking of using more than one card. Perhaps if RDMA is
capabilities are added to Linux, then things might be different.
So.. when do you think RDMA will show up on Linx?
next prev parent reply other threads:[~2003-06-17 20:24 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
2003-06-17 19:50 ` David S. Miller
2003-06-17 20:24 ` Janice M Girouard [this message]
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=3EEF78F4.2070604@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).