From: Jesse Pollard <jesse@cats-chateau.net>
To: Jeff Garzik <jgarzik@pobox.com>, David griego <dagriego@hotmail.com>
Cc: alan@storlinksemi.com, linux-kernel@vger.kernel.org
Subject: Re: Alan Shih: "TCP IP Offloading Interface"
Date: Tue, 15 Jul 2003 07:42:01 -0500 [thread overview]
Message-ID: <03071507420100.27793@tabby> (raw)
In-Reply-To: <3F1303FA.8080706@pobox.com>
On Monday 14 July 2003 14:26, Jeff Garzik wrote:
> David griego wrote:
> > How does one measure the reliability and security of current software
> > TCP/IP stacks? Some standard set of test would have to be identified
> > and the TOEs would need to be tested against this to ensure that they
> > meet some minimum standard. I would suggest offloading the minimum
> > amount from the OS so that most of the control could be maintaind by the
> > OS stack. This also would make failover/routing changes between TOE
> > -TOE, and TOE-NIC easier.
>
> Anything beyond basic host-only TOE adds massive complexity for very
> little gain: interfacing netfilter and routing code with a black box we
> _hope_ will act properly sounds like suicide.
>
> > Current offloads such as checksum and
> >
> > segmentation will not be enough for 10GbE processing, so it would have
> > to be something more than we have today.
>
> All this is vague handwaving without supporting evidence. So far we get
> stuff like Internet2 speed records _without_ TOE. And Linux currently
> supports 10gige... and hosts are just going to keep getting faster and
> faster.
>
> Jeff
Not to mention the problems IPSec would have with such a device.
next prev parent reply other threads:[~2003-07-15 12:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 19:14 Alan Shih: "TCP IP Offloading Interface" David griego
2003-07-14 19:26 ` Jeff Garzik
2003-07-15 12:42 ` Jesse Pollard [this message]
2003-07-14 19:46 ` Alan Cox
[not found] <Sea2-F66GGORm1u51rM00012573@hotmail.com>
2003-07-15 11:18 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-07-14 21:51 David griego
2003-07-14 20:29 David griego
2003-07-14 20:23 David griego
2003-07-14 20:19 David griego
2003-07-14 20:31 ` Alan Shih
2003-07-14 20:34 ` Alan Cox
2003-07-14 21:53 ` Deepak Saxena
2003-07-17 22:31 ` Bill Davidsen
2003-07-14 19:43 David griego
2003-07-14 20:03 ` Jeff Garzik
2003-07-14 20:23 ` Alan Cox
2003-07-14 20:05 ` Alan Cox
2003-07-14 20:30 ` Shawn
2003-07-15 5:58 ` Werner Almesberger
2003-07-14 18:46 David griego
2003-07-14 19:02 ` Jeff Garzik
2003-07-14 21:22 ` Deepak Saxena
2003-07-14 21:45 ` Jeff Garzik
2003-07-15 5:27 ` Werner Almesberger
2003-07-14 19:42 ` 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=03071507420100.27793@tabby \
--to=jesse@cats-chateau.net \
--cc=alan@storlinksemi.com \
--cc=dagriego@hotmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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).