From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Dennis Cook <cook@sandgate.com>
Cc: linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org
Subject: Re: Deactivating TCP checksumming
Date: Wed, 2 Apr 2003 16:03:02 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0304021555160.32710@chaos> (raw)
In-Reply-To: <b6fi8m$j4g$1@main.gmane.org>
On Wed, 2 Apr 2003, Dennis Cook wrote:
> What I was looking for is a general capability to keep the SW transport
> stack from
> computing outgoing TCP/UDP/IP checksums so that the HW can be allowed to do
> it,
> similar to Windows checksum offload capability.
REALLY? Who are you kidding. Windows has no such capability.
Check \WINDOWS\SYSTEM32\DRIVERS\ETC\* and see who they stole
the TCP/IP stack from!
Further, when you perform normal user->TCP/IP operations, you
get checksumming for free as part of the copy operation. It's
only when you don't even copy data that you can get any advantage
of not checksumming. That's why sendfile disables it.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.
next prev parent reply other threads:[~2003-04-02 20:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 12:12 shesha bhushan
2003-04-01 12:28 ` Matti Aarnio
2003-04-02 19:22 ` Dennis Cook
2003-04-02 20:36 ` Jeff Garzik
2003-04-02 20:47 ` Dennis Cook
2003-04-02 20:58 ` Jeff Garzik
2003-04-03 20:34 ` Dennis Cook
2003-04-03 20:47 ` Jeff Garzik
2003-04-03 20:57 ` Dennis Cook
2003-04-04 14:20 ` Jeff Garzik
2003-04-04 14:08 ` Abhishek Agrawal
2003-04-04 4:41 ` Ion Badulescu
2003-04-02 21:03 ` Richard B. Johnson [this message]
2003-04-02 21:22 ` Dennis Cook
-- strict thread matches above, loose matches on Subject: below --
2003-04-01 9:47 shesha bhushan
2003-04-01 10:58 ` Matti Aarnio
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=Pine.LNX.4.53.0304021555160.32710@chaos \
--to=root@chaos.analogic.com \
--cc=cook@sandgate.com \
--cc=kernelnewbies@nl.linux.org \
--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®