|To:||Thomas Graf <tgraf@xxxxxxx>|
|From:||"David S. Miller" <davem@xxxxxxxxxxxxx>|
|Date:||Mon, 24 Jan 2005 19:43:28 -0800|
|Cc:||herbert@xxxxxxxxxxxxxxxxxxx, david@xxxxxxxxxxxxxxxx, kaber@xxxxxxxxx, netdev@xxxxxxxxxxx|
|References:||<41F50B6C.6010107@xxxxxxxxxxxxxxxx> <20050124151510.GV23931@xxxxxxxxxxxxxx> <20050124225423.GA15405@xxxxxxxxxxxxxxxxxxx> <20050124234515.GA31837@xxxxxxxxxxxxxx> <20050125000759.GA15883@xxxxxxxxxxxxxxxxxxx> <20050124164049.3b939791.davem@xxxxxxxxxxxxx> <20050125014538.GB31837@xxxxxxxxxxxxxx> <20050125014838.GA16637@xxxxxxxxxxxxxxxxxxx> <20050125020118.GC31837@xxxxxxxxxxxxxx> <20050124180354.63ae600d.davem@xxxxxxxxxxxxx> <20050125022431.GD31837@xxxxxxxxxxxxxx>|
On Tue, 25 Jan 2005 03:24:31 +0100 Thomas Graf <tgraf@xxxxxxx> wrote: > This of course explains it, didn't think of that. I thought it would > inherit the checksumming features. It should, but only in very limited cases. For example, it probably only works properly when HW vlan assist is being used on TX. It's likely that the chips which don't support VLAN assist also can't handle VLAN headers in their TX checksumming engine. Because it is very chip dependant whether this works or not in any case, we should probably create a special features flag for this. Something like NETIF_F_VLAN_INHERIT_FEATURES.
|<Prev in Thread]||Current Thread||[Next in Thread>|