From: Bin Ren <bin.ren@gmail.com>
To: Andrew Theurer <habanero@us.ibm.com>
Cc: Xen-devel@lists.xensource.com, Jon Mason <jdmason@us.ibm.com>
Subject: Re: [PATCH] Network Checksum Removal
Date: Mon, 23 May 2005 17:06:07 +0100 [thread overview]
Message-ID: <8ae7802505052309067d88f174@mail.gmail.com> (raw)
In-Reply-To: <8ae78025050523085662a94019@mail.gmail.com>
Start from fresh again. The same weird symptoms.
- Bin
On 5/23/05, Bin Ren <bin.ren@gmail.com> wrote:
> I'm using bridge and stock scripts. I start to doubt it's caused csum
> offloading, as I'm seeing some weird things. (1) it's possible to do
> interdomain iperf, which binds to ports > 1024 (2) ssh and nfs don't
> work. In both cases, dom0 is the server, dom1 is the client. tcpdump
> on dom0 doesn't show any incoming packets from dom1.
>
> I'm recompiling everything again.
>
> Cheers,
> Bin
>
> On 5/23/05, Andrew Theurer <habanero@us.ibm.com> wrote:
> > On Monday 23 May 2005 10:31, Bin Ren wrote:
> > > It seems to break the interdomain ssh and nfs on my machine. Digging
> > > for reasons.
> >
> > Are you using bridge or network model?
> > >
> > > - Bin
> > >
> > > On 5/23/05, Andrew Theurer <habanero@us.ibm.com> wrote:
> > > > > I've checked in a modified version of your patch that hopefully
> > > > > deals with propagating checksum information in both directions
> > > > > across a virtual bridge or router. I replaced your skb flags with
> > > > > two new ones -- proto_csum_blank and proto_csum_valid.
> > > > >
> > > > > The former indicates that the protocol-level checksum needs
> > > > > filling in. This is not a problem for local processing, but the
> > > > > flag is picked up before sending to a physical interface and
> > > > > fixed up.
> > > > >
> > > > > The latter indicates that the proto-level checksum has been
> > > > > validated since arrival at localhost (*or* that the packet
> > > > > originated from a domU on localhost). This flag survives crossing
> > > > > a bridge/router so we can trust it when deciding if checksum
> > > > > validation is required.
> > > > >
> > > > > I'll push the patch to the bkbits repository just as soon as
> > > > > bkbits rematerialises. :-)
> > > > >
> > > > > If you have any performance or stress tests that you were using
> > > > > to test checksum offloading, it would be great to find out how
> > > > > they perform on the checked-in version!
> > > >
> > > > Now that BK is up, I'll run some netperf tests before/after that
> > > > changeset and see what we get.
> > > >
> > > > -Andrew
> > > >
> > > > _______________________________________________
> > > > Xen-devel mailing list
> > > > Xen-devel@lists.xensource.com
> > > > http://lists.xensource.com/xen-devel
> >
> >
>
next prev parent reply other threads:[~2005-05-23 16:06 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 23:30 [PATCH] Network Checksum Removal 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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-23 20:26 Ian Pratt
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-24 1:22 Ian Pratt
2005-05-24 1:35 ` Bin Ren
2005-05-24 22:54 ` Bin Ren
2005-05-25 16:48 Ian Pratt
2005-05-25 17:13 ` Jon Mason
2005-05-25 18:19 ` Nivedita Singhvi
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
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=8ae7802505052309067d88f174@mail.gmail.com \
--to=bin.ren@gmail.com \
--cc=Xen-devel@lists.xensource.com \
--cc=bin.ren@cl.cam.ac.uk \
--cc=habanero@us.ibm.com \
--cc=jdmason@us.ibm.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.