From: Bharath Madhavan <bharath_madhavan@ivivity.com>
To: "'David S. Miller'" <davem@redhat.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: RE: Accelerated TCP/IP support from kernel
Date: Thu, 24 May 2001 18:50:53 -0400 [thread overview]
Message-ID: <25369470B6F0D41194820002B328BDD20717A0@ATLOPS> (raw)
Thanks a lot. That was useful info especially your last point
where you are saying that most of the area we can save is in
data processing and not in protocol processing.
So, if we use the ZERO_COPY feature, we should gain quite a bit.
I guess 3c905c NIC supports HW checksumming. Is this true?
In this case, do we have any benchmarking for this card
with and without ZERO_COPY (and HW checksumming). I am eager to
know by how many times did the system throughput increase?
Thanks a lot
Bharath
-----Original Message-----
From: David S. Miller [mailto:davem@redhat.com]
Sent: Thursday, May 24, 2001 6:29 PM
To: Bharath Madhavan
Cc: linux-kernel@vger.kernel.org
Subject: Re: Accelerated TCP/IP support from kernel
Bharath Madhavan writes:
> I am looking into a scenario where we have a NIC which performs
> all the TCP/IP processing and basically the core CPU offloads all data
from
> the socket level interface onwards to this NIC.
Why would you ever want to do this?
Point 1: Support for new TCP techniques and bug fixes are hard enough
to propagate to user's systems as it is with the implementation being
done in software.
Point 2: If I find a bug in the cards TCP implementation, will I be
able to get at the source for the firmware and fix it? Likely the
answer to this is no.
Every couple years a few vendors make cards like this, yet ignore
these core issues. It is currently impractical to use these kinds of
cards today except in a few very special case situations.
Furthermore, the actual protocol processing overhead is quite small
and almost neglible especially on today's gigahertz beasts. The data
copy is where the time is spent, and checksum offload takes care of
that.
Later,
David S. Miller
davem@redhat.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-05-24 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 22:50 Bharath Madhavan [this message]
2001-05-24 23:07 ` David S. Miller
2001-05-24 23:51 ` Gerhard Mack
-- strict thread matches above, loose matches on Subject: below --
2001-05-25 13:51 Bharath Madhavan
2001-05-24 22:16 Bharath Madhavan
2001-05-24 22:28 ` David S. Miller
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=25369470B6F0D41194820002B328BDD20717A0@ATLOPS \
--to=bharath_madhavan@ivivity.com \
--cc=davem@redhat.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
all inboxes | Powered by JetHome®