[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Linux TCP Checksum offload limitations


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Fri, 4 Apr 2008 22:04:53 +1100
  • Delivery-date: Fri, 04 Apr 2008 04:05:20 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AciWQ7V8Bs7yhl7zT9mECnz6ZKd7Og==
  • Thread-topic: Linux TCP Checksum offload limitations

Some version of Windows appear to give the network adapter driver a
packet broken up into fairly small pieces, eg
Page 0: 14 bytes of Ethernet Header
Page 1: 20 bytes of IP Header
Page 2: 20 bytes of TCP Header
Page 3: 1460 bytes of TCP Data

When this happens, Linux appears to not pass the packets beyond the
vifX.Y interface - a tcpdump on (say) vif455.0 shows packets but a
tcpdump on eth0 does not show all the packets - packets with a bad
checksum don't make it that far.
 
Our best guess is that the Linux checksum offload code can't cope with
the way Windows is fragmenting the packets, but maybe Xen is somehow
involved in this...

Can someone please confirm that this is a limitation of Linux and/or
Xen?

Thanks

James

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.