From: patchwork-bot+netdevbpf@kernel.org
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com
Subject: Re: [PATCH net-next 0/6] sk_buff: optimize GRO for the common case
Date: Thu, 29 Jul 2021 11:20:06 +0000 [thread overview]
Message-ID: <162755760636.22479.11591702770264272098.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1627405778.git.pabeni@redhat.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 28 Jul 2021 18:23:58 +0200 you wrote:
> This is a trimmed down revision of "sk_buff: optimize layout for GRO",
> specifically dropping the changes to the sk_buff layout[1].
>
> This series tries to accomplish 2 goals:
> - optimize the GRO stage for the most common scenario, avoiding a bunch
> of conditional and some more code
> - let owned skbs entering the GRO engine, allowing backpressure in the
> veth GRO forward path.
>
> [...]
Here is the summary with links:
- [net-next,1/6] sk_buff: introduce 'slow_gro' flags
https://git.kernel.org/netdev/net-next/c/5fc88f93edf2
- [net-next,2/6] sk_buff: track dst status in slow_gro
https://git.kernel.org/netdev/net-next/c/8a886b142bd0
- [net-next,3/6] sk_buff: track extension status in slow_gro
https://git.kernel.org/netdev/net-next/c/b0999f385ac3
- [net-next,4/6] net: optimize GRO for the common case.
https://git.kernel.org/netdev/net-next/c/9efb4b5baf6c
- [net-next,5/6] skbuff: allow 'slow_gro' for skb carring sock reference
https://git.kernel.org/netdev/net-next/c/5e10da5385d2
- [net-next,6/6] veth: use skb_prepare_for_gro()
https://git.kernel.org/netdev/net-next/c/d504fff0d14a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-07-29 11:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 16:23 [PATCH net-next 0/6] sk_buff: optimize GRO for the common case Paolo Abeni
2021-07-28 16:23 ` [PATCH net-next 1/6] sk_buff: introduce 'slow_gro' flags Paolo Abeni
2021-07-28 16:24 ` [PATCH net-next 2/6] sk_buff: track dst status in slow_gro Paolo Abeni
2021-07-30 11:08 ` Jakub Kicinski
2021-07-30 13:08 ` Paolo Abeni
2021-07-28 16:24 ` [PATCH net-next 3/6] sk_buff: track extension " Paolo Abeni
2021-07-28 16:24 ` [PATCH net-next 4/6] net: optimize GRO for the common case Paolo Abeni
2021-07-28 16:24 ` [PATCH net-next 5/6] skbuff: allow 'slow_gro' for skb carring sock reference Paolo Abeni
2021-07-28 16:24 ` [PATCH net-next 6/6] veth: use skb_prepare_for_gro() Paolo Abeni
2021-07-29 11:20 ` 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=162755760636.22479.11591702770264272098.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.