All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dennis Cook" <cook@sandgate.com>
To: linux-kernel@vger.kernel.org
Cc: kernelnewbies@nl.linux.org
Subject: Re: Deactivating TCP checksumming
Date: Wed, 2 Apr 2003 15:47:35 -0500	[thread overview]
Message-ID: <b6fi8m$j4g$1@main.gmane.org> (raw)
In-Reply-To: 20030402203653.GA2503@gtf.org

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.

"Jeff Garzik" <jgarzik@pobox.com> wrote in message
news:20030402203653.GA2503@gtf.org...
> On Wed, Apr 02, 2003 at 02:22:59PM -0500, Dennis Cook wrote:
> > Using RH Linux kernel 2.4.18, setting "features" bit NETIF_F_IP_CSUM
does
> > not appear
> > to keep a valid IP checksum from being computed in packets presented to
my
> > driver
> > for transmission. So having HW compute outgoing checksum buys nothing.
>
> You are not using sendfile(2), which is required to activate h/w csum.
>
> Jeff
>
>
>




  reply	other threads:[~2003-04-02 20:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-01 12:12 Deactivating TCP checksumming 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 [this message]
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
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='b6fi8m$j4g$1@main.gmane.org' \
    --to=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 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.