From: Stefan Kuhne <stefan.kuhne@gmx.net>
To: xen-devel@lists.xensource.com
Subject: Re: Checksumming problem in pv_ops dom0 kernel / netback
Date: Thu, 18 Mar 2010 00:37:02 +0100 [thread overview]
Message-ID: <4BA1679E.4060300@access.denied> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01918F44@trantor>
[-- Attachment #1.1: Type: text/plain, Size: 653 bytes --]
Am 18.03.2010 00:25, schrieb James Harper:
Hello,
> 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've no VLAN running.
But i've only a similar problem.
Regards,
Stefan Kuhne
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 552 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-03-17 23:37 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
2010-03-17 23:37 ` Stefan Kuhne [this message]
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=4BA1679E.4060300@access.denied \
--to=stefan.kuhne@gmx.net \
--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.