netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Edward Cree <ecree@solarflare.com>,
	David Miller <davem@davemloft.net>,
	eric.dumazet@gmail.com
Cc: nic_swsd@realtek.com, netdev@vger.kernel.org, brouer@redhat.com
Subject: Re: [PATCH net-next] r8169: use netif_receive_skb_list batching
Date: Mon, 1 Apr 2019 19:39:06 +0200	[thread overview]
Message-ID: <207c232c-1ade-ff54-4384-76f4d0280a7d@gmail.com> (raw)
In-Reply-To: <f59aa498-673d-3a4a-efb7-256a86fe720b@solarflare.com>

On 01.04.2019 19:31, Edward Cree wrote:
> On 01/04/2019 18:14, David Miller wrote:
>> From: Eric Dumazet <eric.dumazet@gmail.com>
>> Date: Mon, 1 Apr 2019 02:17:12 -0700
>>
>>> This means no GRO at all
>> I do not think that is true as the SKB list layer does queue up to
>> GRO.
> No, Eric is right; the current list layer bypasses GRO completely.
> 
> netif_receive_skb_list() ends up doing the same things netif_receive_skb()
> would do on each SKB in the list, and that does not include GRO.
> (For this reason the sfc driver only uses netif_receive_skb_list() for
> non-TCP packets; TCP packets go to napi_gro_frags().)
> I had a patch series to add napi_gro_receive_list() which would use the
> SKB list layer to handle the packets GRO didn't coalesce ([1]) but the
> performance tests I ran were inconclusive and it never got applied.
> 
> -Ed
> 
> [1]: https://marc.info/?l=linux-netdev&m=154221888012410&w=2
> 
Patch 0a25d92c6f4f ("dpaa2-eth: use netif_receive_skb_list") was well
perceived [1], therefore I was under the assumption that
netif_receive_skb_list is kind of successor for napi_gro_receive().
Does what you say apply to that patch too?

Based on feedback so far it seems to best if I revert the patch.

Heiner

[1] https://patchwork.ozlabs.org/patch/1064334/

      reply	other threads:[~2019-04-01 17:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-31 13:18 [PATCH net-next] r8169: use netif_receive_skb_list batching Heiner Kallweit
2019-03-31 18:11 ` David Miller
2019-04-01  9:17   ` Eric Dumazet
2019-04-01 12:53     ` Jesper Dangaard Brouer
2019-04-01 17:41       ` David Miller
2019-04-01 21:33         ` Eric Dumazet
2019-04-01 17:14     ` David Miller
2019-04-01 17:31       ` Edward Cree
2019-04-01 17:39         ` Heiner Kallweit [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=207c232c-1ade-ff54-4384-76f4d0280a7d@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=brouer@redhat.com \
    --cc=davem@davemloft.net \
    --cc=ecree@solarflare.com \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.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).