[PATCH] ixgbe: add GRO to vlan_features

[PATCH] ixgbe: add GRO to vlan_features

[Brandon Philips]

When running a vlan -> bridge -> domU setup I was noticing poor RX
performance. It seems ixgbe and other drivers don't have NETIF_F_GRO set
in vlan_features and thus GRO is off by default for vlans.

I see no reason why the other drivers shouldn't be fixed. If this is OK
I will go off and fix the rest.

Signed-off-by: Brandon Philips <bphilips@suse.de>

---
 drivers/net/ixgbe/ixgbe_main.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/drivers/net/ixgbe/ixgbe_main.c b/drivers/net/ixgbe/ixgbe_main.c
index d03eef9..0b39757 100644
--- a/drivers/net/ixgbe/ixgbe_main.c
+++ b/drivers/net/ixgbe/ixgbe_main.c
@@ -6817,6 +6817,7 @@ static int __devinit ixgbe_probe(struct pci_dev *pdev,
 	netdev->vlan_features |= NETIF_F_IP_CSUM;
 	netdev->vlan_features |= NETIF_F_IPV6_CSUM;
 	netdev->vlan_features |= NETIF_F_SG;
+	netdev->vlan_features |= NETIF_F_GRO;
 
 	if (adapter->flags & IXGBE_FLAG_SRIOV_ENABLED)
 		adapter->flags &= ~(IXGBE_FLAG_RSS_ENABLED |
-- 
1.7.1


------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit http://communities.intel.com/community/wired

Re: [PATCH] ixgbe: add GRO to vlan_features

[David Miller]

From: Brandon Philips <bphilips@suse.de>
Date: Tue, 14 Sep 2010 18:50:53 -0700

> When running a vlan -> bridge -> domU setup I was noticing poor RX
> performance. It seems ixgbe and other drivers don't have NETIF_F_GRO set
> in vlan_features and thus GRO is off by default for vlans.
> 
> I see no reason why the other drivers shouldn't be fixed. If this is OK
> I will go off and fix the rest.
> 
> Signed-off-by: Brandon Philips <bphilips@suse.de>

I think it should be set, but why don't we do this another way?

This feature is a software feature, essentially, so if it is published
in netdev->features we can simply propagate it automatically to
netdev->vlan_features at device registry time in the core networking.

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit http://communities.intel.com/community/wired

[PATCH] vlan: enable GRO if real_dev supports it

[Brandon Philips]

Currently vlan devices don't have GRO by default as none of the Ethernet
drivers add NETIF_F_GRO to their vlan_features.

As GRO is a software feature just propogate GRO from the real_dev in the
vlan core. There is no need to have the drivers each add NETIF_F_GRO to
their vlan_features.

Signed-off-by: Brandon Philips <bphilips@suse.de>
---
 net/8021q/vlan_dev.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/net/8021q/vlan_dev.c b/net/8021q/vlan_dev.c
index 3bccdd1..6fbc445 100644
--- a/net/8021q/vlan_dev.c
+++ b/net/8021q/vlan_dev.c
@@ -735,6 +735,7 @@ static int vlan_dev_init(struct net_device *dev)
 					  (1<<__LINK_STATE_DORMANT))) |
 		      (1<<__LINK_STATE_PRESENT);
 
+	dev->features |= real_dev->features & NETIF_F_GRO;
 	dev->features |= real_dev->features & real_dev->vlan_features;
 	dev->gso_max_size = real_dev->gso_max_size;
 
-- 
1.7.1

Re: [PATCH] ixgbe: add GRO to vlan_features

[Brandon Philips]

On 21:35 Tue 14 Sep 2010, David Miller wrote:
> From: Brandon Philips <bphilips@suse.de>
> Date: Tue, 14 Sep 2010 18:50:53 -0700
> 
> > When running a vlan -> bridge -> domU setup I was noticing poor RX
> > performance. It seems ixgbe and other drivers don't have NETIF_F_GRO set
> > in vlan_features and thus GRO is off by default for vlans.
> > 
> > I see no reason why the other drivers shouldn't be fixed. If this is OK
> > I will go off and fix the rest.
> > 
> > Signed-off-by: Brandon Philips <bphilips@suse.de>
> 
> I think it should be set, but why don't we do this another way?
> 
> This feature is a software feature, essentially, so if it is published
> in netdev->features we can simply propagate it automatically to
> netdev->vlan_features at device registry time in the core networking.

Agreed. I will just send a patch to vlan_dev.c then.

Re: [PATCH] vlan: enable GRO if real_dev supports it

[Eric Dumazet]

Le mercredi 15 septembre 2010 à 09:37 -0700, Brandon Philips a écrit :
> Currently vlan devices don't have GRO by default as none of the Ethernet
> drivers add NETIF_F_GRO to their vlan_features.
> 
> As GRO is a software feature just propogate GRO from the real_dev in the
> vlan core. There is no need to have the drivers each add NETIF_F_GRO to
> their vlan_features.
> 
> Signed-off-by: Brandon Philips <bphilips@suse.de>
> ---
>  net/8021q/vlan_dev.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/net/8021q/vlan_dev.c b/net/8021q/vlan_dev.c
> index 3bccdd1..6fbc445 100644
> --- a/net/8021q/vlan_dev.c
> +++ b/net/8021q/vlan_dev.c
> @@ -735,6 +735,7 @@ static int vlan_dev_init(struct net_device *dev)
>  					  (1<<__LINK_STATE_DORMANT))) |
>  		      (1<<__LINK_STATE_PRESENT);
>  
> +	dev->features |= real_dev->features & NETIF_F_GRO;
>  	dev->features |= real_dev->features & real_dev->vlan_features;
>  	dev->gso_max_size = real_dev->gso_max_size;
>  

Hmm, this is only part of a generic solution.

If I enable gro with "ethtool -K eth0 gro on", should we propagate GRO
on vlan eth0.555 ?

Re: [PATCH] vlan: enable GRO if real_dev supports it

[David Miller]

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Wed, 15 Sep 2010 19:08:40 +0200

> Le mercredi 15 septembre 2010 à 09:37 -0700, Brandon Philips a écrit :
>> Currently vlan devices don't have GRO by default as none of the Ethernet
>> drivers add NETIF_F_GRO to their vlan_features.
>> 
>> As GRO is a software feature just propogate GRO from the real_dev in the
>> vlan core. There is no need to have the drivers each add NETIF_F_GRO to
>> their vlan_features.
>> 
>> Signed-off-by: Brandon Philips <bphilips@suse.de>
>> ---
>>  net/8021q/vlan_dev.c |    1 +
>>  1 files changed, 1 insertions(+), 0 deletions(-)
>> 
>> diff --git a/net/8021q/vlan_dev.c b/net/8021q/vlan_dev.c
>> index 3bccdd1..6fbc445 100644
>> --- a/net/8021q/vlan_dev.c
>> +++ b/net/8021q/vlan_dev.c
>> @@ -735,6 +735,7 @@ static int vlan_dev_init(struct net_device *dev)
>>  					  (1<<__LINK_STATE_DORMANT))) |
>>  		      (1<<__LINK_STATE_PRESENT);
>>  
>> +	dev->features |= real_dev->features & NETIF_F_GRO;
>>  	dev->features |= real_dev->features & real_dev->vlan_features;
>>  	dev->gso_max_size = real_dev->gso_max_size;
>>  
> 
> Hmm, this is only part of a generic solution.
> 
> If I enable gro with "ethtool -K eth0 gro on", should we propagate GRO
> on vlan eth0.555 ?

I think a better way to implement this is to set NETIF_F_GRO in
netdev->vlan_features at register_netdev() time if it is set in
netdev->features

That is the implementation I was implying earlier in this thread.

Re: [PATCH] vlan: enable GRO if real_dev supports it

[Ben Hutchings]

On Wed, 2010-09-15 at 10:14 -0700, David Miller wrote:
> From: Eric Dumazet <eric.dumazet@gmail.com>
> Date: Wed, 15 Sep 2010 19:08:40 +0200
> 
> > Le mercredi 15 septembre 2010 à 09:37 -0700, Brandon Philips a écrit :
> >> Currently vlan devices don't have GRO by default as none of the Ethernet
> >> drivers add NETIF_F_GRO to their vlan_features.
> >> 
> >> As GRO is a software feature just propogate GRO from the real_dev in the
> >> vlan core. There is no need to have the drivers each add NETIF_F_GRO to
> >> their vlan_features.
> >> 
> >> Signed-off-by: Brandon Philips <bphilips@suse.de>
> >> ---
> >>  net/8021q/vlan_dev.c |    1 +
> >>  1 files changed, 1 insertions(+), 0 deletions(-)
> >> 
> >> diff --git a/net/8021q/vlan_dev.c b/net/8021q/vlan_dev.c
> >> index 3bccdd1..6fbc445 100644
> >> --- a/net/8021q/vlan_dev.c
> >> +++ b/net/8021q/vlan_dev.c
> >> @@ -735,6 +735,7 @@ static int vlan_dev_init(struct net_device *dev)
> >>  					  (1<<__LINK_STATE_DORMANT))) |
> >>  		      (1<<__LINK_STATE_PRESENT);
> >>  
> >> +	dev->features |= real_dev->features & NETIF_F_GRO;
> >>  	dev->features |= real_dev->features & real_dev->vlan_features;
> >>  	dev->gso_max_size = real_dev->gso_max_size;
> >>  
> > 
> > Hmm, this is only part of a generic solution.
> > 
> > If I enable gro with "ethtool -K eth0 gro on", should we propagate GRO
> > on vlan eth0.555 ?
> 
> I think a better way to implement this is to set NETIF_F_GRO in
> netdev->vlan_features at register_netdev() time if it is set in
> netdev->features
> 
> That is the implementation I was implying earlier in this thread.

We can even add it unconditionally there, since we only ever use
dev->features & dev->vlan_features.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

Re: [PATCH] vlan: enable GRO if real_dev supports it

[David Miller]

From: Ben Hutchings <bhutchings@solarflare.com>
Date: Wed, 15 Sep 2010 18:24:36 +0100

> On Wed, 2010-09-15 at 10:14 -0700, David Miller wrote:
>> I think a better way to implement this is to set NETIF_F_GRO in
>> netdev->vlan_features at register_netdev() time if it is set in
>> netdev->features
>> 
>> That is the implementation I was implying earlier in this thread.
> 
> We can even add it unconditionally there, since we only ever use
> dev->features & dev->vlan_features.

Good point!

Re: [PATCH] vlan: enable GRO if real_dev supports it

[Brandon Philips]

On 19:08 Wed 15 Sep 2010, Eric Dumazet wrote:
> Le mercredi 15 septembre 2010 à 09:37 -0700, Brandon Philips a écrit :
> > Currently vlan devices don't have GRO by default as none of the Ethernet
> > drivers add NETIF_F_GRO to their vlan_features.
> > 
> > As GRO is a software feature just propogate GRO from the real_dev in the
> > vlan core. There is no need to have the drivers each add NETIF_F_GRO to
> > their vlan_features.
> > 
> > Signed-off-by: Brandon Philips <bphilips@suse.de>
> > ---
> >  net/8021q/vlan_dev.c |    1 +
> >  1 files changed, 1 insertions(+), 0 deletions(-)
> > 
> > diff --git a/net/8021q/vlan_dev.c b/net/8021q/vlan_dev.c
> > index 3bccdd1..6fbc445 100644
> > --- a/net/8021q/vlan_dev.c
> > +++ b/net/8021q/vlan_dev.c
> > @@ -735,6 +735,7 @@ static int vlan_dev_init(struct net_device *dev)
> >  					  (1<<__LINK_STATE_DORMANT))) |
> >  		      (1<<__LINK_STATE_PRESENT);
> >  
> > +	dev->features |= real_dev->features & NETIF_F_GRO;
> >  	dev->features |= real_dev->features & real_dev->vlan_features;
> >  	dev->gso_max_size = real_dev->gso_max_size;
> >  
> 
> Hmm, this is only part of a generic solution.
> 
> If I enable gro with "ethtool -K eth0 gro on", should we propagate GRO
> on vlan eth0.555 ?

That works fine as far as I can see. I don't think it should go the
other way though. 

Cheers, Brandon

[PATCH] net: enable GRO by default for vlan devices

[Brandon Philips]

Currently vlan devices don't have GRO by default as none of the Ethernet
drivers add NETIF_F_GRO to their vlan_features.

As GRO is a software feature add GRO to dev->vlan_features in
register_netdevice() and let vlan_dev_init() take care that it gets
enabled only when dev->features has NETIF_F_GRO too.

Signed-off-by: Brandon Philips <bphilips@suse.de>

---
 net/core/dev.c |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/net/core/dev.c b/net/core/dev.c
index fc2dc93..e7a6bff 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -5057,6 +5057,11 @@ int register_netdevice(struct net_device *dev)
 	if (dev->features & NETIF_F_SG)
 		dev->features |= NETIF_F_GSO;
 
+	/* Enable GRO for vlans by default if dev->features has GRO also. 
+	 * vlan_dev_init() will do the dev->features check.
+	 */
+	dev->vlan_features |= NETIF_F_GRO;
+
 	ret = call_netdevice_notifiers(NETDEV_POST_INIT, dev);
 	ret = notifier_to_errno(ret);
 	if (ret)
-- 
1.7.1


------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit http://communities.intel.com/community/wired

Re: [PATCH] net: enable GRO by default for vlan devices

[Eric Dumazet]

Le mercredi 15 septembre 2010 à 12:24 -0700, Brandon Philips a écrit :
> Currently vlan devices don't have GRO by default as none of the Ethernet
> drivers add NETIF_F_GRO to their vlan_features.
> 
> As GRO is a software feature add GRO to dev->vlan_features in
> register_netdevice() and let vlan_dev_init() take care that it gets
> enabled only when dev->features has NETIF_F_GRO too.
> 
> Signed-off-by: Brandon Philips <bphilips@suse.de>
> 

Acked-by: Eric Dumazet <eric.dumazet@gmail.com>

Re: [PATCH] net: enable GRO by default for vlan devices

[Eric Dumazet]

Le jeudi 16 septembre 2010 à 00:03 +0200, Eric Dumazet a écrit :
> Le mercredi 15 septembre 2010 à 12:24 -0700, Brandon Philips a écrit :
> > Currently vlan devices don't have GRO by default as none of the Ethernet
> > drivers add NETIF_F_GRO to their vlan_features.
> > 
> > As GRO is a software feature add GRO to dev->vlan_features in
> > register_netdevice() and let vlan_dev_init() take care that it gets
> > enabled only when dev->features has NETIF_F_GRO too.
> > 
> > Signed-off-by: Brandon Philips <bphilips@suse.de>
> > 
> 
> Acked-by: Eric Dumazet <eric.dumazet@gmail.com>
> 

BTW, we have a similar problem for bonding ( GRO is disabled )

# ethtool -K bond0 gro off
# ethtool -K bond0 gro on
Cannot set device GRO settings: Invalid argument

Same for vlans on top of bond0




------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit http://communities.intel.com/community/wired

Re: [PATCH] net: enable GRO by default for vlan devices

[Stephen Hemminger]

On Thu, 16 Sep 2010 00:28:11 +0200
Eric Dumazet <eric.dumazet@gmail.com> wrote:

> Le jeudi 16 septembre 2010 à 00:03 +0200, Eric Dumazet a écrit :
> > Le mercredi 15 septembre 2010 à 12:24 -0700, Brandon Philips a écrit :
> > > Currently vlan devices don't have GRO by default as none of the Ethernet
> > > drivers add NETIF_F_GRO to their vlan_features.
> > > 
> > > As GRO is a software feature add GRO to dev->vlan_features in
> > > register_netdevice() and let vlan_dev_init() take care that it gets
> > > enabled only when dev->features has NETIF_F_GRO too.
> > > 
> > > Signed-off-by: Brandon Philips <bphilips@suse.de>
> > > 
> > 
> > Acked-by: Eric Dumazet <eric.dumazet@gmail.com>
> > 
> 
> BTW, we have a similar problem for bonding ( GRO is disabled )
> 
> # ethtool -K bond0 gro off
> # ethtool -K bond0 gro on
> Cannot set device GRO settings: Invalid argument
> 
> Same for vlans on top of bond0

Bridge has same problem as well.


-- 

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit http://communities.intel.com/community/wired

Re: [PATCH] net: enable GRO by default for vlan devices

[David Miller]

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 16 Sep 2010 00:03:23 +0200

> Le mercredi 15 septembre 2010 à 12:24 -0700, Brandon Philips a écrit :
>> Currently vlan devices don't have GRO by default as none of the Ethernet
>> drivers add NETIF_F_GRO to their vlan_features.
>> 
>> As GRO is a software feature add GRO to dev->vlan_features in
>> register_netdevice() and let vlan_dev_init() take care that it gets
>> enabled only when dev->features has NETIF_F_GRO too.
>> 
>> Signed-off-by: Brandon Philips <bphilips@suse.de>
>> 
> 
> Acked-by: Eric Dumazet <eric.dumazet@gmail.com>

Applied.

Re: [E1000-devel] [PATCH] net: enable GRO by default for vlan devices

[David Miller]

From: Stephen Hemminger <shemminger@vyatta.com>
Date: Wed, 15 Sep 2010 18:16:16 -0700

> On Thu, 16 Sep 2010 00:28:11 +0200
> Eric Dumazet <eric.dumazet@gmail.com> wrote:
> 
>> BTW, we have a similar problem for bonding ( GRO is disabled )
>> 
>> # ethtool -K bond0 gro off
>> # ethtool -K bond0 gro on
>> Cannot set device GRO settings: Invalid argument
>> 
>> Same for vlans on top of bond0
> 
> Bridge has same problem as well.

Looking this over it should be a simple matter of:

1) Adding the generic get/set gro ethtool ops to bonding
   and bridge device ops.

2) Set NETIF_F_GRO in bond/bridge device flags

3) Maybe some minor fiddling with netdev_increment_features
   and the flag macros it uses?

Patches welcome :-)

Re: [E1000-devel] [PATCH] net: enable GRO by default for vlan devices

[Stephen Hemminger]

On Wed, 15 Sep 2010 22:51:46 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:

> From: Stephen Hemminger <shemminger@vyatta.com>
> Date: Wed, 15 Sep 2010 18:16:16 -0700
> 
> > On Thu, 16 Sep 2010 00:28:11 +0200
> > Eric Dumazet <eric.dumazet@gmail.com> wrote:
> > 
> >> BTW, we have a similar problem for bonding ( GRO is disabled )
> >> 
> >> # ethtool -K bond0 gro off
> >> # ethtool -K bond0 gro on
> >> Cannot set device GRO settings: Invalid argument
> >> 
> >> Same for vlans on top of bond0
> > 
> > Bridge has same problem as well.
> 
> Looking this over it should be a simple matter of:
> 
> 1) Adding the generic get/set gro ethtool ops to bonding
>    and bridge device ops.
> 
> 2) Set NETIF_F_GRO in bond/bridge device flags
> 
> 3) Maybe some minor fiddling with netdev_increment_features
>    and the flag macros it uses?
> 
> Patches welcome :-)

I think it is more complex than that. GRO is tied to NAPI,
and bridge/bond don't use NAPI directly. They use netif_rx() for receiving
because layered drivers can't directly up call because of possible
issues with stack depth. 

To get GRO working for netif_rx case,
the logic in process_backlog would have to change.
But this queue is processing packets from multiple devices so
it is not clear if GRO could be used.


-- 

Re: [E1000-devel] [PATCH] net: enable GRO by default for vlan devices

[David Miller]

From: Stephen Hemminger <shemminger@vyatta.com>
Date: Wed, 15 Sep 2010 23:21:25 -0700

> I think it is more complex than that. GRO is tied to NAPI,
> and bridge/bond don't use NAPI directly. They use netif_rx() for receiving
> because layered drivers can't directly up call because of possible
> issues with stack depth. 
> 
> To get GRO working for netif_rx case,
> the logic in process_backlog would have to change.
> But this queue is processing packets from multiple devices so
> it is not clear if GRO could be used.

Bonding's un-layering on RX is done in the normal netif_receive_skb()
control flow.

And bridging only uses netif_rx for multicast replication.

Re: [E1000-devel] [PATCH] net: enable GRO by default for vlan devices

[Eric Dumazet]

Le mercredi 15 septembre 2010 à 23:38 -0700, David Miller a écrit :
> From: Stephen Hemminger <shemminger@vyatta.com>
> Date: Wed, 15 Sep 2010 23:21:25 -0700
> 
> > I think it is more complex than that. GRO is tied to NAPI,
> > and bridge/bond don't use NAPI directly. They use netif_rx() for receiving
> > because layered drivers can't directly up call because of possible
> > issues with stack depth. 
> > 
> > To get GRO working for netif_rx case,
> > the logic in process_backlog would have to change.
> > But this queue is processing packets from multiple devices so
> > it is not clear if GRO could be used.
> 
> Bonding's un-layering on RX is done in the normal netif_receive_skb()
> control flow.
> 
> And bridging only uses netif_rx for multicast replication.

Yes, bonding case should be easy, I'll take a look today.

[PATCH] ethtool: change ethtool_set_gro() to use ethtool_op_get_rx_csum

[Eric Dumazet]

Le jeudi 16 septembre 2010 à 08:43 +0200, Eric Dumazet a écrit :
> Le mercredi 15 septembre 2010 à 23:38 -0700, David Miller a écrit :
> > From: Stephen Hemminger <shemminger@vyatta.com>
> > Date: Wed, 15 Sep 2010 23:21:25 -0700
> > 
> > > I think it is more complex than that. GRO is tied to NAPI,
> > > and bridge/bond don't use NAPI directly. They use netif_rx() for receiving
> > > because layered drivers can't directly up call because of possible
> > > issues with stack depth. 
> > > 
> > > To get GRO working for netif_rx case,
> > > the logic in process_backlog would have to change.
> > > But this queue is processing packets from multiple devices so
> > > it is not clear if GRO could be used.
> > 
> > Bonding's un-layering on RX is done in the normal netif_receive_skb()
> > control flow.
> > 
> > And bridging only uses netif_rx for multicast replication.
> 
> Yes, bonding case should be easy, I'll take a look today.
> 

[PATCH] ethtool: change ethtool_set_gro() to use ethtool_op_get_rx_csum

To be able to switch on GRO on a device, ethtool_set_gro() checks this
device provides a get_rx_csum() method.

Some devices dont provide this method, while they do support RX
checksumming.

This patch allows bonding to support GRO :

ethtool -K bond0 gro on

Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
---
 net/core/ethtool.c |    7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/net/core/ethtool.c b/net/core/ethtool.c
index 7a85367..8c8c6d4 100644
--- a/net/core/ethtool.c
+++ b/net/core/ethtool.c
@@ -1175,8 +1175,11 @@ static int ethtool_set_gro(struct net_device *dev, char __user *useraddr)
 		return -EFAULT;
 
 	if (edata.data) {
-		if (!dev->ethtool_ops->get_rx_csum ||
-		    !dev->ethtool_ops->get_rx_csum(dev))
+		u32 rxcsum = dev->ethtool_ops->get_rx_csum ?
+				dev->ethtool_ops->get_rx_csum(dev) :
+				ethtool_op_get_rx_csum(dev);
+
+		if (!rxcsum)
 			return -EINVAL;
 		dev->features |= NETIF_F_GRO;
 	} else

Re: [PATCH] ethtool: change ethtool_set_gro() to use ethtool_op_get_rx_csum

[David Miller]

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 16 Sep 2010 10:11:03 +0200

> [PATCH] ethtool: change ethtool_set_gro() to use ethtool_op_get_rx_csum
> 
> To be able to switch on GRO on a device, ethtool_set_gro() checks this
> device provides a get_rx_csum() method.
> 
> Some devices dont provide this method, while they do support RX
> checksumming.
> 
> This patch allows bonding to support GRO :
> 
> ethtool -K bond0 gro on
> 
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>

Applied, thanks Eric.

Can you do whatever change is needed to get it enabled by default?

Thanks again.

[PATCH] bonding: enable gro by default

[Eric Dumazet]

Le vendredi 17 septembre 2010 à 11:57 -0700, David Miller a écrit :

> Applied, thanks Eric.
> 
> Can you do whatever change is needed to get it enabled by default?
> 

Sure ;)

[PATCH] bonding: enable gro by default

gro can be enabled by default on bonding devices.

Actual support depends on the lower devices.

One can still use ethtool to switch off GRO if needed.

Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
---
 drivers/net/bonding/bond_main.c |    4 ++++
 1 file changed, 4 insertions(+)

diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
index 3b16f62..80610a6 100644
--- a/drivers/net/bonding/bond_main.c
+++ b/drivers/net/bonding/bond_main.c
@@ -4678,6 +4678,10 @@ static void bond_setup(struct net_device *bond_dev)
 			       NETIF_F_HW_VLAN_RX |
 			       NETIF_F_HW_VLAN_FILTER);
 
+	/* By default, we enable GRO on bonding devices.
+	 * Actual support requires lowlevel drivers are GRO ready.
+	 */
+	bond_dev->features |= NETIF_F_GRO;
 }
 
 static void bond_work_cancel_all(struct bonding *bond)

Re: [PATCH] bonding: enable gro by default

[David Miller]

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 17 Sep 2010 21:25:07 +0200

> gro can be enabled by default on bonding devices.
> 
> Actual support depends on the lower devices.
> 
> One can still use ethtool to switch off GRO if needed.
> 
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>

Applied, thanks Eric.

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit http://communities.intel.com/community/wired