[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1364695805.3557.41.camel@deadeye.wl.decadent.org.uk>
Date: Sun, 31 Mar 2013 03:10:05 +0100
From: Ben Hutchings <ben@...adent.org.uk>
To: "Huang, Xiong" <xiong@....qualcomm.com>
Cc: Anders Boström <anders@...insight.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"565404@...s.debian.org" <565404@...s.debian.org>,
"Hannes Frederic Sowa (hannes@...essinduktion.org)"
<hannes@...essinduktion.org>
Subject: Re: Bug#565404: linux-image-2.6.26-2-amd64: atl1e: TSO is broken
On Sun, 2013-03-31 at 02:18 +0000, Huang, Xiong wrote:
> > > >
> > > > I've tested with
> > > > Debian linux-image-2.6.26-2-amd64 version 2.6.26-19lenny2, Debian
> > > > linux-image-2.6.30-bpo.2-amd64 version 2.6.30-8~bpo50+2 and
> > > > kernel.org
> > > > 2.6.30.10 amd64 with ethtool patch for setting of tso. Same result.
> > >
> > > Does booting with the kernel parameter 'pci=nomsi' avoid the problem?
> > >
> >
> > Hannes has found DMA-write (for rx-packet) is abnormal due to msi function.
> > But TSO is for rx-packet, an opposite direction. I'm not sure :(, If someone
> > has this issue, he/she could have a try.
> >
>
> I checked windows driver, it does limit the max packet length for TSO
> windows XP : 32*1024 bytes (include MAC header and all MAC payload). No support IP/TCP option.
> Windows 7: 15, 000 bytes, support IP/TCP option.
If TSO on these devices don't work properly with TCP options then you're
just going to have to disable it - Linux requires it to support at least
the timestamp option. I'm not sure about IP options (this really ought
to be documented).
If there's a length limit lower than 64K, you'll need to set the limit
using netif_set_gso_max_size() before registering the net device.
Ben.
--
Ben Hutchings
Teamwork is essential - it allows you to blame someone else.
Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)
Powered by blists - more mailing lists