[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <160210320307.20743.18344305972350266676.git-patchwork-notify@kernel.org>
Date: Wed, 07 Oct 2020 20:40:03 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Magnus Karlsson <magnus.karlsson@...il.com>
Cc: magnus.karlsson@...el.com, bjorn.topel@...el.com, ast@...nel.org,
daniel@...earbox.net, netdev@...r.kernel.org,
jonathan.lemon@...il.com, bpf@...r.kernel.org,
ciara.loftus@...el.com
Subject: Re: [PATCH bpf-next v2] libbpf: fix compatibility problem in
xsk_socket__create
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Wed, 7 Oct 2020 13:42:26 +0200 you wrote:
> From: Magnus Karlsson <magnus.karlsson@...el.com>
>
> Fix a compatibility problem when the old XDP_SHARED_UMEM mode is used
> together with the xsk_socket__create() call. In the old XDP_SHARED_UMEM
> mode, only sharing of the same device and queue id was allowed, and in
> this mode, the fill ring and completion ring were shared between the
> AF_XDP sockets. Therefore, it was perfectly fine to call the
> xsk_socket__create() API for each socket and not use the new
> xsk_socket__create_shared() API. This behavior was ruined by the
> commit introducing XDP_SHARED_UMEM support between different devices
> and/or queue ids. This patch restores the ability to use
> xsk_socket__create in these circumstances so that backward
> compatibility is not broken.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] libbpf: fix compatibility problem in xsk_socket__create
https://git.kernel.org/bpf/bpf-next/c/80348d8867c6
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