From: Jeff Garzik <jgarzik@pobox.com>
To: David griego <dagriego@hotmail.com>
Cc: alan@storlinksemi.com, linux-kernel@vger.kernel.org
Subject: Re: Alan Shih: "TCP IP Offloading Interface"
Date: Mon, 14 Jul 2003 15:02:35 -0400 [thread overview]
Message-ID: <3F12FE4B.2070004@pobox.com> (raw)
In-Reply-To: <Sea2-F18ekWo76UaiRN00008964@hotmail.com>
David griego wrote:
> IMHO, there are several cases for some type of TCP/IP offload. One is
> for embedded systems that are just not capable of doing 1Gbps+. Another
> is with 10GbE, even high end servers will not be able keep up with TCP
> processing/data movement at these speeds. Not being proactive in
> adopting TCP/IP offload will force Linux into accepting some scheme that
> will not necissarily be best.
How does one evaluate a TOE stack to be sure that all the security fixes
in Linux are also in that stack?
How does one evaluate a TOE stack to be sure it doesn't add new security
holes that Linux never had?
Jeff
next prev parent reply other threads:[~2003-07-14 18:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 18:46 Alan Shih: "TCP IP Offloading Interface" David griego
2003-07-14 19:02 ` Jeff Garzik [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-07-14 19:14 David griego
2003-07-14 19:26 ` Jeff Garzik
2003-07-15 12:42 ` Jesse Pollard
2003-07-14 19:46 ` Alan Cox
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 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 20:23 David griego
2003-07-14 20:29 David griego
2003-07-14 21:51 David griego
[not found] <Sea2-F66GGORm1u51rM00012573@hotmail.com>
2003-07-15 11:18 ` 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=3F12FE4B.2070004@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@storlinksemi.com \
--cc=dagriego@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.