From: patchwork-bot+netdevbpf@kernel.org
To: Magnus Karlsson <magnus.karlsson@gmail.com>
Cc: magnus.karlsson@intel.com, bjorn@kernel.org, ast@kernel.org,
daniel@iogearbox.net, netdev@vger.kernel.org,
maciej.fijalkowski@intel.com, yuvale@radware.com,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/2] xsk: support redirect to any socket bound to the same umem
Date: Tue, 06 Feb 2024 04:10:26 +0000 [thread overview]
Message-ID: <170719262634.31872.11192144503118658406.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240205123553.22180-1-magnus.karlsson@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 5 Feb 2024 13:35:49 +0100 you wrote:
> This patch set adds support for directing a packet to any socket bound
> to the same umem. This makes it possible to use the XDP program to
> select what socket the packet should be received on. The user can
> populate the XSKMAP with various sockets and as long as they share the
> same umem, the XDP program can pick any one of them.
>
> The implementation is straight-forward. Instead of testing that the
> incoming packet is targeting the same device and queue id as the
> socket is bound to, just check that the umem the packet was received
> on is the same as the socket we want it to be received on. This
> guarantees that the redirect is legal as it is already in the correct
> umem.
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] xsk: support redirect to any socket bound to the same umem
https://git.kernel.org/bpf/bpf-next/c/2863d665ea41
- [bpf-next,2/2] xsk: document ability to redirect to any socket bound to the same umem
https://git.kernel.org/bpf/bpf-next/c/968595a93669
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-02-06 4:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 12:35 [PATCH bpf-next 0/2] xsk: support redirect to any socket bound to the same umem Magnus Karlsson
2024-02-05 12:35 ` [PATCH bpf-next 1/2] " Magnus Karlsson
2024-02-05 14:26 ` Willem de Bruijn
2024-02-05 12:35 ` [PATCH bpf-next 2/2] xsk: document ability to " Magnus Karlsson
2024-02-06 4:10 ` 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=170719262634.31872.11192144503118658406.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@gmail.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=yuvale@radware.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