From: patchwork-bot+netdevbpf@kernel.org
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
steffen.klassert@secunet.com, willemb@google.com, alobakin@pm.me
Subject: Re: [PATCH net-next v3 0/8] udp: GRO L4 improvements
Date: Wed, 31 Mar 2021 00:20:10 +0000 [thread overview]
Message-ID: <161715001053.3850.9092742275313404295.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1617099959.git.pabeni@redhat.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 30 Mar 2021 12:28:48 +0200 you wrote:
> This series improves the UDP L4 - either 'forward' or 'frag_list' -
> co-existence with UDP tunnel GRO, allowing the first to take place
> correctly even for encapsulated UDP traffic.
>
> The first for patches are mostly bugfixes, addressing some GRO
> edge-cases when both tunnels and L4 are present, enabled and in use.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/8] udp: fixup csum for GSO receive slow path
https://git.kernel.org/netdev/net-next/c/000ac44da7d0
- [net-next,v3,2/8] udp: skip L4 aggregation for UDP tunnel packets
https://git.kernel.org/netdev/net-next/c/18f25dc39990
- [net-next,v3,3/8] udp: properly complete L4 GRO over UDP tunnel packet
https://git.kernel.org/netdev/net-next/c/e0e3070a9bc9
- [net-next,v3,4/8] udp: never accept GSO_FRAGLIST packets
https://git.kernel.org/netdev/net-next/c/78352f73dc50
- [net-next,v3,5/8] vxlan: allow L4 GRO passthrough
https://git.kernel.org/netdev/net-next/c/d18931a92a0b
- [net-next,v3,6/8] geneve: allow UDP L4 GRO passthrou
https://git.kernel.org/netdev/net-next/c/61630c4f052b
- [net-next,v3,7/8] bareudp: allow UDP L4 GRO passthrou
https://git.kernel.org/netdev/net-next/c/b03ef676ba6d
- [net-next,v3,8/8] selftests: net: add UDP GRO forwarding self-tests
https://git.kernel.org/netdev/net-next/c/a062260a9d5f
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-03-31 0:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 10:28 [PATCH net-next v3 0/8] udp: GRO L4 improvements Paolo Abeni
2021-03-30 10:28 ` [PATCH net-next v3 1/8] udp: fixup csum for GSO receive slow path Paolo Abeni
2021-03-30 15:15 ` Willem de Bruijn
2021-03-30 10:28 ` [PATCH net-next v3 2/8] udp: skip L4 aggregation for UDP tunnel packets Paolo Abeni
2021-03-30 10:28 ` [PATCH net-next v3 3/8] udp: properly complete L4 GRO over UDP tunnel packet Paolo Abeni
2021-03-30 10:28 ` [PATCH net-next v3 4/8] udp: never accept GSO_FRAGLIST packets Paolo Abeni
2021-03-30 15:14 ` Willem de Bruijn
2021-03-30 10:28 ` [PATCH net-next v3 5/8] vxlan: allow L4 GRO passthrough Paolo Abeni
2021-03-30 15:14 ` Willem de Bruijn
2021-03-30 10:28 ` [PATCH net-next v3 6/8] geneve: allow UDP L4 GRO passthrou Paolo Abeni
2021-03-30 10:28 ` [PATCH net-next v3 7/8] bareudp: " Paolo Abeni
2021-03-30 10:28 ` [PATCH net-next v3 8/8] selftests: net: add UDP GRO forwarding self-tests Paolo Abeni
2021-03-30 15:49 ` Willem de Bruijn
2021-03-31 0: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=161715001053.3850.9092742275313404295.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alobakin@pm.me \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.com \
--cc=willemb@google.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.