From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>, Jesse Gross <jesse@nicira.com>
Subject: [BUG] bnx2 + vlan + TSO : doesnt work
Date: Tue, 18 Jan 2011 00:41:09 +0100 [thread overview]
Message-ID: <1295307669.3362.106.camel@edumazet-laptop> (raw)
Oh well, my dev machine, with bnx2 and tg3 NICs, isnt working at all
with current linux-2.6 tree (I need vlans on my setup)
tg3 : vlan not working
bnx2 : vlan + TSO not working (or very slowly, since only non GSO frames
are OK)
I suspect recent commits from Jesse are the problem.
(bnx2_xmit() is feeded with zeroed vlan_tci skbs)
Maybe f01a5236bd4b1401 (net offloading: Generalize
netif_get_vlan_features().) ?
I dont see NETIF_F_HW_VLAN_TX being set in vlan_features in net drivers.
They only set this flag in dev->features
I dont think changing all drivers to also set vlan_features makes sense.
Is following patch the right path ? (It does solve my problem)
diff --git a/net/core/dev.c b/net/core/dev.c
index 54277df..5c13e55 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -5265,6 +5265,9 @@ int register_netdevice(struct net_device *dev)
*/
dev->vlan_features |= (NETIF_F_GRO | NETIF_F_HIGHDMA);
+ /* allow netif_skb_features() not mask this bit from dev->features */
+ dev->vlan_features |= NETIF_F_HW_VLAN_TX;
+
ret = call_netdevice_notifiers(NETDEV_POST_INIT, dev);
ret = notifier_to_errno(ret);
if (ret)
next reply other threads:[~2011-01-17 23:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 23:41 Eric Dumazet [this message]
2011-01-17 23:47 ` [BUG] bnx2 + vlan + TSO : doesnt work Ben Hutchings
2011-01-18 0:00 ` Eric Dumazet
2011-01-18 0:09 ` Ben Hutchings
2011-01-18 0:13 ` Jesse Gross
2011-01-18 6:09 ` David Miller
2011-01-18 6:21 ` Eric Dumazet
2011-01-18 6:32 ` Jesse Gross
2011-01-18 6:38 ` Eric Dumazet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1295307669.3362.106.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox