From: Matt Porter <mporter@kernel.crashing.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org,
linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: TCP IP Offloading Interface
Date: Tue, 15 Jul 2003 19:46:49 -0700 [thread overview]
Message-ID: <20030715194649.D8616@home.com> (raw)
In-Reply-To: <20030713174242.3ceb8213.davem@redhat.com>; from davem@redhat.com on Sun, Jul 13, 2003 at 05:42:42PM -0700
On Sun, Jul 13, 2003 at 05:42:42PM -0700, David S. Miller wrote:
> There are cards, both existing and in development, that have
> very simple header parsing engines you can program to do stuff
> like this, it isn't hard at all.
Do you have a reference to an existing card that implements
a header parsing engine like this (and has obtainable docs)?
Regards,
--
Matt Porter
mporter@kernel.crashing.org
next prev parent reply other threads:[~2003-07-16 2:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-13 7:33 TCP IP Offloading Interface Alan Shih
2003-07-13 7:48 ` David S. Miller
2003-07-13 16:22 ` 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 [this message]
2003-07-14 0:20 ` Roland Dreier
2003-07-14 0:28 ` David S. Miller
2003-07-16 2:37 ` Matt Porter
2003-07-13 14:51 ` Jeff Garzik
[not found] <E3738FB497C72449B0A81AEABE6E713C027A43@STXCHG1.simpletech.com>
2003-07-15 5:51 ` David S. Miller
2003-07-16 5:02 ` jamal
2003-07-16 1:51 ` Roland Dreier
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=20030715194649.D8616@home.com \
--to=mporter@kernel.crashing.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=davem@redhat.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).