From: Shan Wei <shanwei@cn.fujitsu.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: "David Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
"Eric Dumazet" <eric.dumazet@gmail.com>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"therbert@google.com" <therbert@google.com>
Subject: Re: [RFC][NET-NEXT PATCH 2/2] net: Add GSO to vlan_features initialization
Date: Sat, 02 Jul 2011 15:07:43 +0800 [thread overview]
Message-ID: <4E0EC3BF.1060107@cn.fujitsu.com> (raw)
In-Reply-To: <4E094EE7.1000203@cn.fujitsu.com>
Hi Ben:
Shan Wei wrote, at 06/28/2011 11:47 AM:
> Hi Ben:
>
> Ben Hutchings wrote, at 06/25/2011 12:51 AM:
>> Have you verified that GSO works correctly for VLAN devices if the
>> underlying device does not support VLAN tag insertion?
>
> OK. I will do some test in future days.
> Then report test results.
Results is coming....
GSO works correctly for VLAN devices when
underlying device is Realtek NIC with 8139too driver.
Network tracepoint shows as following:
<Begin:
tcpclient-5915 [000] 2114.246780: net_dev_queue: dev=eth1.44 skbaddr=f3051bc0 len=74
tcpclient-5915 [000] 2114.246790: net_dev_queue: dev=eth1 skbaddr=f3051bc0 len=74
tcpclient-5915 [000] 2114.246798: net_dev_xmit: dev=eth1 skbaddr=f3051bc0 len=78 rc=0
tcpclient-5915 [000] 2114.246799: net_dev_xmit: dev=eth1.44 skbaddr=f3051bc0 len=74 rc=0
<idle>-0 [000] 2114.246905: net_dev_queue: dev=eth1.44 skbaddr=f73cc480 len=66
<idle>-0 [000] 2114.246908: net_dev_queue: dev=eth1 skbaddr=f73cc480 len=66
<idle>-0 [000] 2114.246911: net_dev_xmit: dev=eth1 skbaddr=f73cc480 len=70 rc=0
<idle>-0 [000] 2114.246912: net_dev_xmit: dev=eth1.44 skbaddr=f73cc480 len=66 rc=0
tcpclient-5915 [000] 2114.247109: net_dev_queue: dev=eth1.44 skbaddr=f3051bc0 len=2962
tcpclient-5915 [000] 2114.247121: net_dev_queue: dev=eth1 skbaddr=f73cc380 len=1514
tcpclient-5915 [000] 2114.247130: net_dev_xmit: dev=eth1 skbaddr=f73cc380 len=1518 rc=0
tcpclient-5915 [000] 2114.247131: net_dev_xmit: dev=eth1.44 skbaddr=f73cc380 len=1514 rc=0
tcpclient-5915 [000] 2114.247132: net_dev_queue: dev=eth1 skbaddr=f73cc480 len=1514
tcpclient-5915 [000] 2114.247138: net_dev_xmit: dev=eth1 skbaddr=f73cc480 len=1518 rc=0
tcpclient-5915 [000] 2114.247139: net_dev_xmit: dev=eth1.44 skbaddr=f73cc480 len=1514 rc=0
end:>
But, test case requires following two patches:
1. Fix broken vlan GSO setting
[PATCH 1/2] net: vlan: enable GSO by default
http://patchwork.ozlabs.org/patch/101714/
2. Fix my 8139too NIC driver that does not initial vlan_features.
diff --git a/drivers/net/8139too.c b/drivers/net/8139too.c
--- a/drivers/net/8139too.c
+++ b/drivers/net/8139too.c
@@ -993,6 +993,7 @@ static int __devinit rtl8139_init_one (struct pci_dev *pdev,
* features
*/
dev->features |= NETIF_F_SG | NETIF_F_HW_CSUM | NETIF_F_HIGHDMA;
+ dev->vlan_features = dev->features;
--
Best Regards
-----
Shan Wei
prev parent reply other threads:[~2011-07-02 7:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 3:38 [RFC][NET-NEXT PATCH 2/2] net: Add GSO to vlan_features initialization Shan Wei
2011-06-24 16:51 ` Ben Hutchings
2011-06-28 3:47 ` Shan Wei
2011-07-02 7:07 ` Shan Wei [this message]
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=4E0EC3BF.1060107@cn.fujitsu.com \
--to=shanwei@cn.fujitsu.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.com \
/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;
as well as URLs for NNTP newsgroup(s).