From: Ben Hutchings <bhutchings@solarflare.com>
To: Shan Wei <shanwei@cn.fujitsu.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: Fri, 24 Jun 2011 17:51:42 +0100 [thread overview]
Message-ID: <1308934302.3034.4.camel@bwh-desktop> (raw)
In-Reply-To: <4E0406BE.50900@cn.fujitsu.com>
On Fri, 2011-06-24 at 11:38 +0800, Shan Wei wrote:
> This patch is not a bug fix.
> Just add GSO to vlan_features initialization, and update comments.
>
>
> Signed-off-by: Shan Wei <shanwei@cn.fujitsu.com>
> ---
> net/core/dev.c | 9 +++++----
> 1 files changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/net/core/dev.c b/net/core/dev.c
> index 6b6ef14..becc1e5 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -5478,11 +5478,12 @@ int register_netdevice(struct net_device *dev)
> dev->features |= NETIF_F_NOCACHE_COPY;
> }
>
> - /* Enable GRO and NETIF_F_HIGHDMA for vlans by default,
> - * vlan_dev_init() will do the dev->features check, so these features
> - * are enabled only if supported by underlying device.
> + /* Enable GSO, GRO and NETIF_F_HIGHDMA for vlans by default,
> + * vlan_dev_fix_features() will do the features check,
> + * so NETIF_F_HIGHDMA feature is enabled only if supported
> + * by underlying device.
> */
> - dev->vlan_features |= (NETIF_F_GRO | NETIF_F_HIGHDMA);
> + dev->vlan_features |= (NETIF_F_SOFT_FEATURES | NETIF_F_HIGHDMA);
>
> ret = call_netdevice_notifiers(NETDEV_POST_INIT, dev);
> ret = notifier_to_errno(ret);
Have you verified that GSO works correctly for VLAN devices if the
underlying device does not support VLAN tag insertion?
skb_gso_segment() has code to handle this case, but I suspect it's not
actually being exercised at the moment.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2011-06-24 16:51 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 [this message]
2011-06-28 3:47 ` Shan Wei
2011-07-02 7:07 ` Shan Wei
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=1308934302.3034.4.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=netdev@vger.kernel.org \
--cc=shanwei@cn.fujitsu.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.