From: Jeff Garzik <jgarzik@pobox.com>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: Werner Almesberger <werner@almesberger.net>,
netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: TOE brain dump
Date: Sat, 02 Aug 2003 15:08:52 -0400 [thread overview]
Message-ID: <3F2C0C44.6020002@pobox.com> (raw)
In-Reply-To: <3F2BF5C7.90400@us.ibm.com>
My own brain dump:
If one wants to go straight from disk to network, why is anyone
bothering to involve the host CPU and host memory bus at all? Memory
bandwidth and PCI bus bandwidth are still bottlenecks, no much how much
of the net stack you offload.
Regardless of how fast your network zooms packets, you've gotta keep
that pipeline full to make use of it. And you've gotta do something
intelligent with it, which in TCP's case involves the host CPU quite a
bit. TCP is sufficiently complex, for a reason. It has to handle all
manner of disturbingly slow and disturbing fast net connections, all
jabbering at the same time. TCP is a "one size fits all" solution, but
it doesn't work well for everyone.
The "TCP Offload Everything" people really need to look at what data
your users want to push, at such high speeds. It's obviously not over a
WAN... so steer users away from TCP, to an IP protocol that is tuned
for your LAN needs, and more friendly to some sort of h/w offloading
solution.
A "foo over ipv6" protocol that was designed for h/w offloading from the
start, would be a far better idea than full TCP offload will ever be.
In any case, when you approach these high speeds, you really must take a
good look at the other end of the pipeline: what are you serving at
10Gb/s, 20Gb/s, 40Gb/s? For some time, I think the answer will be
"highly specialized stuff" At some point, Intel networking gear will be
able to transfer more bits per second than there exist atoms on planet
Earth :) Garbage in, garbage out.
So, fix the other end of the pipeline too, otherwise this fast network
stuff is flashly but pointless. If you want to serve up data from disk,
then start creating PCI cards that have both Serial ATA and ethernet
connectors on them :) Cut out the middleman of the host CPU and host
memory bus instead of offloading portions of TCP that do not need to be
offloaded.
Jeff
next prev parent reply other threads:[~2003-08-02 19:09 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 17:04 TOE brain dump Werner Almesberger
2003-08-02 17:32 ` Nivedita Singhvi
2003-08-02 18:06 ` Werner Almesberger
2003-08-02 19:08 ` Jeff Garzik [this message]
2003-08-02 21:49 ` Werner Almesberger
2003-08-03 6:40 ` Jeff Garzik
2003-08-03 17:57 ` Werner Almesberger
2003-08-03 18:27 ` Erik Andersen
2003-08-03 19:40 ` Larry McVoy
2003-08-03 20:13 ` David Lang
2003-08-03 20:30 ` Larry McVoy
2003-08-03 21:21 ` David Lang
2003-08-03 23:44 ` Larry McVoy
2003-08-03 21:58 ` Jeff Garzik
2003-08-05 19:28 ` Timothy Miller
2003-08-03 20:34 ` jamal
2003-08-04 1:47 ` Glen Turner
2003-08-04 3:48 ` Larry McVoy
2003-08-06 7:12 ` Andre Hedrick
[not found] ` <Pine.LNX.4.10.10308060009130.25045-100000@master.linux-ide .org>
2003-08-06 8:20 ` Lincoln Dale
2003-08-06 8:22 ` David S. Miller
2003-08-06 13:07 ` Jesse Pollard
2003-08-03 19:21 ` Eric W. Biederman
2003-08-04 19:24 ` Werner Almesberger
2003-08-04 19:26 ` David S. Miller
2003-08-05 17:19 ` Eric W. Biederman
2003-08-06 5:13 ` Werner Almesberger
2003-08-06 7:58 ` Eric W. Biederman
2003-08-06 13:37 ` Werner Almesberger
2003-08-06 15:58 ` Andy Isaacson
2003-08-06 16:27 ` Chris Friesen
2003-08-06 17:01 ` Andy Isaacson
2003-08-06 17:55 ` Matti Aarnio
2003-08-07 2:14 ` Lincoln Dale
2003-08-06 12:46 ` Jesse Pollard
2003-08-06 16:25 ` Andy Isaacson
2003-08-06 18:58 ` Jesse Pollard
2003-08-06 19:39 ` Andy Isaacson
2003-08-06 21:13 ` David Schwartz
2003-08-03 4:01 ` Ben Greear
2003-08-03 6:22 ` Alan Shih
2003-08-03 6:41 ` Jeff Garzik
2003-08-03 8:25 ` David Lang
2003-08-03 18:05 ` Werner Almesberger
2003-08-03 22:02 ` Alan Shih
2003-08-03 20:52 ` Alan Cox
2003-08-04 14:36 ` Ingo Oeser
2003-08-04 17:19 ` Alan Shih
2003-08-05 8:15 ` Ingo Oeser
2003-08-02 20:57 ` Alan Cox
2003-08-02 22:14 ` Werner Almesberger
2003-08-03 20:51 ` Alan Cox
[not found] <g83n.8vu.9@gated-at.bofh.it>
2003-08-03 12:13 ` Ihar 'Philips' Filipau
2003-08-03 18:10 ` Werner Almesberger
2003-08-04 8:55 ` Ihar 'Philips' Filipau
2003-08-04 13:08 ` Jesse Pollard
2003-08-04 19:32 ` Werner Almesberger
2003-08-04 19:48 ` David Lang
2003-08-04 19:56 ` Werner Almesberger
2003-08-04 20:01 ` David Lang
2003-08-04 20:09 ` Werner Almesberger
2003-08-04 20:24 ` David Lang
2003-08-05 1:38 ` Werner Almesberger
2003-08-05 1:46 ` David Lang
2003-08-05 1:54 ` Larry McVoy
2003-08-05 2:30 ` Werner Almesberger
2003-08-06 1:47 ` Val Henson
2003-08-05 3:04 ` Werner Almesberger
2003-08-04 23:30 ` Peter Chubb
[not found] <gq0f.8bj.9@gated-at.bofh.it>
[not found] ` <gvCD.4mJ.5@gated-at.bofh.it>
[not found] ` <gJmp.7Th.33@gated-at.bofh.it>
[not found] ` <gNpS.2YJ.9@gated-at.bofh.it>
2003-08-04 14:15 ` Ihar 'Philips' Filipau
2003-08-04 14:56 ` Jesse Pollard
2003-08-04 15:51 ` Ihar 'Philips' Filipau
2003-08-04 18:36 Perez-Gonzalez, Inaky
2003-08-04 19:03 ` Alan Cox
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=3F2C0C44.6020002@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=niv@us.ibm.com \
--cc=werner@almesberger.net \
/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).