[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <EA929A9653AAE14F841771FB1DE5A1365F59F11911@rrsmsx501.amr.corp.intel.com>
Date: Fri, 16 Jan 2009 18:06:18 -0700
From: "Tantilov, Emil S" <emil.s.tantilov@...el.com>
To: Herbert Xu <herbert@...dor.apana.org.au>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
CC: "David S. Miller" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: ixgbe: Replace LRO with GRO
See attached.
Thanks,
Emil
-----Original Message-----
From: Herbert Xu [mailto:herbert@...dor.apana.org.au]
Sent: Friday, January 16, 2009 4:36 PM
To: Kirsher, Jeffrey T
Cc: David S. Miller; netdev@...r.kernel.org; Tantilov, Emil S
Subject: Re: ixgbe: Replace LRO with GRO
On Fri, Jan 16, 2009 at 03:32:56PM -0800, Jeff Kirsher wrote:
>
> Adding Emil to provide further testing details...
>
> We are seeing data corruption with this patch applied. When we
> disable GRO the data corruption goes away.
>
> We have this simple ftp test that does put/get and then compares
> md5sum of the file. The file we get back is different then the one we
> sent with GRO enabled. The file is around 34MB. Note that we don't
> always see the corruption with 30meg file, but it becomes more
> apparent as we increase the size of the file.
>
> If this helps - Emil did a diff off of a hexdump output between the
> sent and received file. Looks like the receive was cut off at the end:
Thanks for the info Jeff!
As the file isn't too big, could you do two packet dumps, one
at the sender and one at the receiver? Capturing just the headers
should be sufficient for now.
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Download attachment "gro_corruption.tar.gz" of type "application/x-gzip" (92972 bytes)
Powered by blists - more mailing lists