All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <nsnix@comcast.net>
To: Jason <xen@jasonandjessi.com>
Cc: Florian Kirstein <ray-re@ray.net>, xen-devel@lists.xensource.com
Subject: Re: networking checksum errors again
Date: Sat, 01 Apr 2006 13:44:01 -0800	[thread overview]
Message-ID: <442EF421.2080708@comcast.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0603311020140.11893@localhost>

Jason wrote:
> w00t!  That fixed it.  I read your email on the logic for not doing the 
> tcp checksums and, while I
> am by no means in possesion of the brains the developers have, I am left 
> wondering why that
> decision was made.  Would anyone care to comment?
> 
I think I missed a post somewhere along this thread...

Which decision are you referring to? Avoiding the
TCP checksum between domains? The rationale for not
doing the checksum is that it is a significant savings
in performance. Even for traffic that goes out to
a public net and must contain a checksum, deferring
it to dom0 when the OS can offload it to the physical
NIC (most NICs these days are capable of computing the
checksums in hardware) is a significant saving.

The native Linux stack offloads the calculation of
the checksum to the NIC, and not doing so in the virtual
environment increases the gap when comparing Xen to
bare metal Linux.

There are a lot of other issues here to resolve, of
course, and fixing some of the current issues is being
worked. It's likely going to be an issue for discussion
when we're up for mainline inclusion.

thanks,
Nivedita

  reply	other threads:[~2006-04-01 21:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31  5:30 networking checksum errors again Jason
2006-03-31  5:46 ` Florian Kirstein
2006-03-31  7:10   ` Jason
     [not found]     ` <20060331083153.F26981@web.ray.net>
2006-03-31 16:21       ` Jason
2006-04-01 21:44         ` Nivedita Singhvi [this message]
2006-04-01 23:55           ` Jason

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=442EF421.2080708@comcast.net \
    --to=nsnix@comcast.net \
    --cc=ray-re@ray.net \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen@jasonandjessi.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.