public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Anirban Chakraborty <abchak@juniper.net>
Cc: Wei Liu <wei.liu2@citrix.com>,
	"<netdev@vger.kernel.org>" <netdev@vger.kernel.org>,
	"<xen-devel@lists.xen.org>" <xen-devel@lists.xen.org>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH net-next] xen-netfront: convert to GRO API and advertise this feature
Date: Sun, 22 Sep 2013 22:58:27 -0700	[thread overview]
Message-ID: <1379915907.3165.5.camel@edumazet-glaptop> (raw)
In-Reply-To: <D310C490-3B7D-4937-95DC-AFC1682B60BE@juniper.net>

On Sun, 2013-09-22 at 23:09 +0000, Anirban Chakraborty wrote:
> On Sep 22, 2013, at 7:55 AM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> 
> > On Sat, 2013-09-21 at 17:05 +0100, Wei Liu wrote:
> >> Anirban was seeing netfront received MTU size packets, which downgraded
> >> throughput. The following patch makes netfront use GRO API which
> >> improves throughput for that case.
> > 
> >> -	netdev->hw_features	= NETIF_F_IP_CSUM | NETIF_F_SG | NETIF_F_TSO;
> >> +	netdev->hw_features	= NETIF_F_IP_CSUM | NETIF_F_SG | NETIF_F_TSO |
> >> +				  NETIF_F_GRO;
> > 
> > 
> > This part is not needed.
> 
> Shouldn't the flag be set? In dev_gro_receive() we do check if this flag is set or not:
> 
>         if (!(skb->dev->features & NETIF_F_GRO) || netpoll_rx_on(skb))
>                goto normal;

Drivers do not set NETIF_F_GRO themselves, they do not need to.

Look at other drivers which are GRO ready : NETIF_F_GRO is enabled by
default by core networking stack, in register_netdevice()


dev->hw_features |= NETIF_F_SOFT_FEATURES;
dev->features |= NETIF_F_SOFT_FEATURES;

  reply	other threads:[~2013-09-23  5:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-21 16:05 [PATCH net-next] xen-netfront: convert to GRO API and advertise this feature Wei Liu
2013-09-22  6:29 ` [Xen-devel] " Jason Wang
2013-09-22 12:09   ` Wei Liu
2013-09-22 23:04     ` Anirban Chakraborty
2013-09-23  5:02       ` Jason Wang
2013-09-23  6:22         ` annie li
2013-09-23 20:32           ` Anirban Chakraborty
2013-09-22 14:55 ` Eric Dumazet
2013-09-22 23:09   ` Anirban Chakraborty
2013-09-23  5:58     ` Eric Dumazet [this message]
2013-09-23 20:27       ` Anirban Chakraborty
2013-09-24 16:30 ` [Xen-devel] " Konrad Rzeszutek Wilk
2013-09-28 19:38 ` David Miller
2013-09-30  9:12   ` Ian Campbell
2013-09-30 14:43     ` [Xen-devel] " Konrad Rzeszutek Wilk

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=1379915907.3165.5.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=abchak@juniper.net \
    --cc=ian.campbell@citrix.com \
    --cc=netdev@vger.kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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