From: "David S. Miller" <davem@redhat.com>
To: "Alan Shih" <alan@storlinksemi.com>
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
netdev@oss.sgi.com
Subject: Re: TCP IP Offloading Interface
Date: Sun, 13 Jul 2003 00:48:18 -0700 [thread overview]
Message-ID: <20030713004818.4f1895be.davem@redhat.com> (raw)
In-Reply-To: <ODEIIOAOPGGCDIKEOPILCEMBCMAA.alan@storlinksemi.com>
On Sun, 13 Jul 2003 00:33:00 -0700
"Alan Shih" <alan@storlinksemi.com> wrote:
> Or TOE is a forbidden discussion?
TOE is evil, read this:
http://www.usenix.org/events/hotos03/tech/full_papers/mogul/mogul.pdf
TOE is exactly suboptimal for the very things performance
matters, high connection rates.
Your return is also absolutely questionable. Servers "serve" data
and we offload all of the send side TCP processing that can
reasonably be done (segmentation, checksumming).
I've never seen an impartial benchmark showing that TCP send
side performance goes up as a result of using TOE vs. the usual
segmentation + checksum offloading offered today.
On receive side, clever RX buffer flipping tricks are the way
to go and require no protocol changes and nothing gross like
TOE or weird buffer ownership protocols like RDMA requires.
I've made postings showing how such a scheme can work using a limited
flow cache on the networking card. I don't have a reference handy,
but I suppose someone else does.
And finally, this discussion belongs on the "networking" lists.
Nearly all of the "networking" developers don't have time to sift
through linux-kernel every day.
next parent reply other threads:[~2003-07-13 7:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ODEIIOAOPGGCDIKEOPILCEMBCMAA.alan@storlinksemi.com>
2003-07-13 7:48 ` David S. Miller [this message]
2003-07-13 16:22 ` TCP IP Offloading Interface Roland Dreier
2003-07-13 16:31 ` Alan Cox
2003-07-13 16:49 ` Jeff Garzik
2003-07-13 16:58 ` Jeff Garzik
2003-07-13 23:02 ` David S. Miller
2003-07-13 23:35 ` Larry McVoy
2003-07-13 23:40 ` David S. Miller
2003-07-13 23:54 ` Larry McVoy
2003-07-13 23:53 ` David S. Miller
2003-07-14 0:22 ` Larry McVoy
2003-07-14 0:24 ` David S. Miller
2003-07-14 0:48 ` Larry McVoy
2003-07-14 0:46 ` Valdis.Kletnieks
2003-07-14 0:42 ` David S. Miller
2003-07-16 2:46 ` Matt Porter
2003-07-14 0:20 ` Roland Dreier
2003-07-14 0:28 ` David S. Miller
2003-07-16 2:37 ` Matt Porter
2003-07-15 5:42 Jordi Ros
2003-07-15 5:51 ` David S. Miller
2003-07-16 5:02 ` jamal
2003-07-16 1:51 ` Roland Dreier
2003-07-15 19:01 ` Ralph Doncaster
2003-07-15 19:36 ` Chris Dukes
-- strict thread matches above, loose matches on Subject: below --
2003-07-15 16:28 David griego
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=20030713004818.4f1895be.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@storlinksemi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.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).