From: "James Harper" <james.harper@bendigoit.com.au>
To: "S.H. Verbrugge" <ief@soleus.nu>, xen-devel@lists.xensource.com
Subject: RE: Checksumming problem in pv_ops dom0 kernel / netback
Date: Thu, 18 Mar 2010 10:25:34 +1100 [thread overview]
Message-ID: <AEC6C66638C05B468B556EA548C1A77D01918F44@trantor> (raw)
In-Reply-To: <20100317154848.GE16370@alpha.trueline.nl>
>
> Yeah, I've seen that. It does not give that much information however.
>
> More specifically, I've tested with two dom0 pv_ops kernels now, and
since
> it's still
> reproducable on the latest xen/stable platform, I'm guessing it either
has to
> do with vlan'ing or
> the tg3 driver , in combination with netback.
>
> I was hoping some Xen developers could shed some light on this.
> I already conversed with Jeremy about this, and he pointed me to this
mailing
> list.
>
This may not be relavant, but I have seen problems with the following
combination:
br0:
eth0
<netback devices>
br1:
eth0.2
<netback devices>
Some (most?) network hardware cannot provide checksum/large send offload
functions for packets that use vlan tagging, but Linux doesn't quite
understand that and gets confused, so when such a packet comes off of
netback and is sent to eth0.2, the LSO/checksum function should be
performed in software but isn't.
I haven't yet figured out of the problem is that the driver is
incorrectly reporting that offload is supported on the vlan device or if
the rest of Linux isn't taking the appropriate action...
James
next prev parent reply other threads:[~2010-03-17 23:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 12:34 Checksumming problem in pv_ops dom0 kernel / netback S.H. Verbrugge
2010-03-17 12:48 ` Stefan Kuhne
2010-03-17 15:48 ` S.H. Verbrugge
2010-03-17 23:25 ` James Harper [this message]
2010-03-17 23:37 ` Stefan Kuhne
2010-03-17 23:48 ` S.H. Verbrugge
2010-03-18 0:04 ` James Harper
2010-03-18 0:17 ` S.H. Verbrugge
2010-03-30 22:58 ` Scott Garron
2010-04-14 17:27 ` Pasi Kärkkäinen
2010-04-15 8:20 ` Ian Campbell
2010-05-22 11:51 ` Pasi Kärkkäinen
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=AEC6C66638C05B468B556EA548C1A77D01918F44@trantor \
--to=james.harper@bendigoit.com.au \
--cc=ief@soleus.nu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).