Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH bpf-next V4] xsk: allow remap of fill and/or completion rings
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <167980391993.14901.17617558767037665298.git-patchwork-notify@kernel.org>
Date:   Sun, 26 Mar 2023 04:11:59 +0000
References: <20230324100222.13434-1-nunog@fr24.com>
In-Reply-To: <20230324100222.13434-1-nunog@fr24.com>
To:     =?utf-8?q?Nuno_Gon=C3=A7alves_=3Cnunog=40fr24=2Ecom=3E?=@ci.codeaurora.org
Cc:     bjorn@kernel.org, magnus.karlsson@intel.com,
        maciej.fijalkowski@intel.com, jonathan.lemon@gmail.com,
        davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
        pabeni@redhat.com, brauner@kernel.org, ast@kernel.org,
        daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com,
        netdev@vger.kernel.org, bpf@vger.kernel.org,
        linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.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