[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167980391993.14901.17617558767037665298.git-patchwork-notify@kernel.org>
Date: Sun, 26 Mar 2023 04:11:59 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Nuno Gonçalves <nunog@...4.com>@ci.codeaurora.org
Cc: bjorn@...nel.org, magnus.karlsson@...el.com,
maciej.fijalkowski@...el.com, jonathan.lemon@...il.com,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, brauner@...nel.org, ast@...nel.org,
daniel@...earbox.net, hawk@...nel.org, john.fastabend@...il.com,
netdev@...r.kernel.org, bpf@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH bpf-next V4] xsk: allow remap of fill and/or completion rings
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.org>:
On Fri, 24 Mar 2023 10:02:22 +0000 you wrote:
> The remap of fill and completion rings was frowned upon as they
> control the usage of UMEM which does not support concurrent use.
> At the same time this would disallow the remap of these rings
> into another process.
>
> A possible use case is that the user wants to transfer the socket/
> UMEM ownership to another process (via SYS_pidfd_getfd) and so
> would need to also remap these rings.
>
> [...]
Here is the summary with links:
- [bpf-next,V4] xsk: allow remap of fill and/or completion rings
https://git.kernel.org/bpf/bpf-next/c/5f5a7d8d8bd4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists