All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	richardbgobert@gmail.com, netdev@vger.kernel.org,
	eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/4] net: gro: cleanups and fast path refinement
Date: Tue, 05 Mar 2024 12:50:31 +0000	[thread overview]
Message-ID: <170964303110.9176.6238299590966925699.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240301193740.3436871-1-edumazet@google.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri,  1 Mar 2024 19:37:36 +0000 you wrote:
> Current GRO stack has a 'fast path' for a subset of drivers,
> users of napi_frags_skb().
> 
> With TCP zerocopy/direct uses, header split at receive is becoming
> more important, and GRO fast path is disabled.
> 
> This series makes GRO (a bit) more efficient for almost all use cases.
> 
> [...]

Here is the summary with links:
  - [net-next,1/4] net: gro: rename skb_gro_header_hard()
    https://git.kernel.org/netdev/net-next/c/93e16ea025d2
  - [net-next,2/4] net: gro: change skb_gro_network_header()
    https://git.kernel.org/netdev/net-next/c/bd56a29c7a4e
  - [net-next,3/4] net: gro: enable fast path for more cases
    https://git.kernel.org/netdev/net-next/c/c7583e9f768e
  - [net-next,4/4] tcp: gro: micro optimizations in tcp[4]_gro_complete()
    https://git.kernel.org/netdev/net-next/c/8f78010b701d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-03-05 12:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 19:37 [PATCH net-next 0/4] net: gro: cleanups and fast path refinement Eric Dumazet
2024-03-01 19:37 ` [PATCH net-next 1/4] net: gro: rename skb_gro_header_hard() Eric Dumazet
2024-03-01 19:37 ` [PATCH net-next 2/4] net: gro: change skb_gro_network_header() Eric Dumazet
2024-03-04  8:28   ` Paolo Abeni
2024-03-04  9:06     ` Eric Dumazet
2024-03-04 10:29       ` Paolo Abeni
2024-03-04 13:04       ` Richard Gobert
2024-03-04 13:14         ` Eric Dumazet
2024-03-01 19:37 ` [PATCH net-next 3/4] net: gro: enable fast path for more cases Eric Dumazet
2024-03-01 19:37 ` [PATCH net-next 4/4] tcp: gro: micro optimizations in tcp[4]_gro_complete() Eric Dumazet
2024-03-04 10:30 ` [PATCH net-next 0/4] net: gro: cleanups and fast path refinement Paolo Abeni
2024-03-05 12:50 ` patchwork-bot+netdevbpf [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=170964303110.9176.6238299590966925699.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardbgobert@gmail.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.