From: Jeff Garzik <jgarzik@pobox.com>
To: David Dillow <dillowd@y12.doe.gov>
Cc: Christopher Keller <cnkeller@interclypse.net>,
linux-kernel@vger.kernel.org
Subject: Re: 3COM 3C990 NIC
Date: Tue, 22 Oct 2002 05:47:14 -0400 [thread overview]
Message-ID: <3DB51EA2.5060106@pobox.com> (raw)
In-Reply-To: 3DB4D9F8.F86ABA4@y12.doe.gov
David Dillow wrote:
> I have a completely reworked version that I expect to be able to release RSN.
> (I know, I know, some of you have heard that before... it just takes time to
> get people around here to sign off on these things. :/)
>
> It will support zero-copy TCP, TCP segmentation offload, and when DaveM's
> IPSEC is in, I'll be able to do hardware offload for that as well.
Cool :)
Will you be submitting this for inclusion in the kernel?
And, what differences exists between the 3c59x and 3c90x hardware, and
3c990? Just IPSEC?
JEff
next prev parent reply other threads:[~2002-10-22 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 4:49 3COM 3C990 NIC Christopher Keller
2002-10-22 4:54 ` David Dillow
2002-10-22 9:47 ` Jeff Garzik [this message]
2002-10-22 14:53 ` David Dillow
2002-10-22 14:37 ` Christopher Keller
2002-10-22 23:13 ` David S. Miller
2002-10-23 3:50 ` David Dillow
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=3DB51EA2.5060106@pobox.com \
--to=jgarzik@pobox.com \
--cc=cnkeller@interclypse.net \
--cc=dillowd@y12.doe.gov \
--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