From: patchwork-bot+netdevbpf@kernel.org
To: Ignat Korchagin <ignat@cloudflare.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-team@cloudflare.com
Subject: Re: [PATCH net v3 0/2] net: veth: ability to toggle GRO and XDP independently
Date: Mon, 18 Mar 2024 12:30:29 +0000 [thread overview]
Message-ID: <171076502961.32045.6145861941709920995.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240313183759.87923-1-ignat@cloudflare.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 13 Mar 2024 19:37:57 +0100 you wrote:
> It is rather confusing that GRO is automatically enabled, when an XDP program
> is attached to a veth interface. Moreover, it is not possible to disable GRO
> on a veth, if an XDP program is attached (which might be desirable in some use
> cases).
>
> Make GRO and XDP independent for a veth interface. udpgro_fwd
>
> [...]
Here is the summary with links:
- [net,v3,1/2] net: veth: do not manipulate GRO when using XDP
https://git.kernel.org/netdev/net/c/d7db7775ea2e
- [net,v3,2/2] selftests: net: veth: test the ability to independently manipulate GRO and XDP
https://git.kernel.org/netdev/net/c/ba5a6476e386
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:[~2024-03-18 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 18:37 [PATCH net v3 0/2] net: veth: ability to toggle GRO and XDP independently Ignat Korchagin
2024-03-13 18:37 ` [PATCH net v3 1/2] net: veth: do not manipulate GRO when using XDP Ignat Korchagin
2024-03-13 18:37 ` [PATCH net v3 2/2] selftests: net: veth: test the ability to independently manipulate GRO and XDP Ignat Korchagin
2024-03-18 12:30 ` 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=171076502961.32045.6145861941709920995.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ignat@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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 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).