Re: [Xen-devel] Re: Trouble with TCP between domUs

To:	dme@xxxxxxx (David Edmondson)
Subject:	Re: [Xen-devel] Re: Trouble with TCP between domUs
From:	Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Date:	Tue, 12 Dec 2006 13:34:30 +1100
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Mon, 11 Dec 2006 18:34:45 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<87lklhph38.fsf@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization:	Core
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	tin/1.7.4-20040225 ("Benbecula") (UNIX) (Linux/2.6.17-rc4 (i686))

David Edmondson <dme@xxxxxxx> wrote:
>
>> When I extended the netback protocol for TSO the idea was that you
>> can also have an extra descriptor for checksum offload that would
>> carry the offsets.
> 
> But that offset is not present today, suggesting that the peer
> receiving the packet must be parsing it to determine where to place
> the checksum (though I couldn't find that code in a quick inspection).

What I meant is that the checksum offload can use the same mechanism
as GSO to pass the offset in a descriptor.  This has not been implemented
yet.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

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

WARNING - OLD ARCHIVES

xen-devel

Re: [Xen-devel] Re: Trouble with TCP between domUs