|To:||Thomas Graf <tgraf@xxxxxxx>|
|From:||"David S. Miller" <davem@xxxxxxxxxxxxx>|
|Date:||Tue, 25 Jan 2005 15:30:20 -0800|
|Cc:||greearb@xxxxxxxxxxxxxxx, herbert@xxxxxxxxxxxxxxxxxxx, david@xxxxxxxxxxxxxxxx, kaber@xxxxxxxxx, netdev@xxxxxxxxxxx|
|References:||<20050124164049.3b939791.davem@xxxxxxxxxxxxx> <20050125014538.GB31837@xxxxxxxxxxxxxx> <20050125014838.GA16637@xxxxxxxxxxxxxxxxxxx> <20050125020118.GC31837@xxxxxxxxxxxxxx> <20050124180354.63ae600d.davem@xxxxxxxxxxxxx> <20050125022431.GD31837@xxxxxxxxxxxxxx> <20050124194328.20a106de.davem@xxxxxxxxxxxxx> <20050125143319.GF31837@xxxxxxxxxxxxxx> <20050125203607.GG31837@xxxxxxxxxxxxxx> <41F6B090.6020602@xxxxxxxxxxxxxxx> <20050125211524.GH31837@xxxxxxxxxxxxxx>|
On Tue, 25 Jan 2005 22:15:24 +0100 Thomas Graf <tgraf@xxxxxxx> wrote: > I thought about this too and actually implemented it but it means to > change all relevant drivers and the only feature that might be > driver specific is checksumming, given I didn't make any mistakes > while checking the drivers for pskb compatibility. It is not only checksumming, but also TSO. TSO, like checksumming, is a feature where the chip must parse the packet to figure out where to do it's work. In fact, TSO is a prime suspect for VLAN problems as the card must duplicate the VLAN headers properly as it chops up the TSO frame into MSS sized pieces.
|<Prev in Thread]||Current Thread||[Next in Thread>|