All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Jon Mason <jdmason@us.ibm.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	Andrew Theurer <habanero@us.ibm.com>,
	xen-devel@lists.xensource.com, bin.ren@cl.cam.ac.uk
Subject: Re: [PATCH] Network Checksum Removal
Date: Wed, 25 May 2005 11:19:52 -0700	[thread overview]
Message-ID: <4294C1C8.5050700@us.ibm.com> (raw)
In-Reply-To: <200505251213.08192.jdmason@us.ibm.com>

Jon Mason wrote:

>>I'm surprised there's much benefit to csum offload on the tx side at all
>>as its almost always done as part of a copy.
> 
> 
> Why?  The tx checksumming is just as expensive as the rx checksumming.

Normally (i.e. non sendfile() case), on the transmit side, you
have to copy the data from user space to kernel space, and
usually, during this step, you perform the checksum operation
for a few extra instructions - you have to take the hit of
pulling in each byte of data in any case.

So checksum offload on the transmit path _normally_ buys you
no throughput gain, and very slight reduction in CPU utilization.
Of course, for every segment sent out (or bunches thereof),
we get an ack back. But checksumming a TCP header (pure
ack case) is again, fairly trivial (20 bytes).


thanks,
Nivedita

  reply	other threads:[~2005-05-25 18:19 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 16:48 [PATCH] Network Checksum Removal Ian Pratt
2005-05-25 17:13 ` Jon Mason
2005-05-25 18:19   ` Nivedita Singhvi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-25 20:06 Ian Pratt
2005-05-25 21:14 ` Keir Fraser
2005-05-25 21:35   ` Jon Mason
2005-05-25 21:40     ` Keir Fraser
2005-05-25 23:41       ` Jon Mason
2005-05-26  8:07         ` Keir Fraser
2005-05-26 13:37           ` Jon Mason
2005-05-25 21:38 ` Cédric Schieli
2005-05-25 21:47   ` Keir Fraser
2005-05-25 21:54     ` Keir Fraser
2005-05-24  1:22 Ian Pratt
2005-05-24  1:35 ` Bin Ren
2005-05-24 22:54 ` Bin Ren
2005-05-23 23:59 Ian Pratt
2005-05-24 16:12 ` Jon Mason
2005-05-24 20:45   ` Andrew Theurer
2005-05-25 14:38     ` Andrew Theurer
2005-05-23 20:26 Ian Pratt
2005-05-23 20:22 Ian Pratt
2005-05-23 20:38 ` Keir Fraser
2005-05-23 20:44   ` Jon Mason
2005-05-23 21:01 ` Bin Ren
2005-05-23 21:09   ` Andrew Theurer
2005-05-20 23:30 Jon Mason
2005-05-21 14:53 ` Keir Fraser
2005-05-21 19:16   ` Keir Fraser
2005-05-21 21:49     ` Jon Mason
2005-05-23 15:29     ` Andrew Theurer
2005-05-23 15:31       ` Bin Ren
2005-05-23 15:47         ` Andrew Theurer
2005-05-23 15:56           ` Bin Ren
2005-05-23 16:06             ` Bin Ren
2005-05-23 16:16               ` Jon Mason
2005-05-23 16:36                 ` Bin Ren
2005-05-23 17:54                   ` Keir Fraser
2005-05-23 18:08                     ` Bin Ren
2005-05-23 18:18                       ` Jon Mason
2005-05-23 18:43                         ` Keir Fraser
2005-05-23 18:53                           ` Bin Ren
2005-05-23 19:55                     ` Bin Ren
2005-05-23 20:13                       ` Keir Fraser
2005-05-23 20:20                         ` Jon Mason
2005-05-23 21:52                         ` Bin Ren
2005-05-23 21:58                         ` Jon Mason
2005-05-23 22:05                           ` Bin Ren
2005-05-23 22:41                             ` Jon Mason
2005-05-23 21:12                       ` Nivedita Singhvi
2005-05-23 21:48                         ` Bin Ren
2005-05-23 23:55                           ` Rolf Neugebauer
2005-05-24  0:38                             ` Bin Ren

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=4294C1C8.5050700@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=bin.ren@cl.cam.ac.uk \
    --cc=habanero@us.ibm.com \
    --cc=jdmason@us.ibm.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.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 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.