From: patchwork-bot+netdevbpf@kernel.org
To: Jalal Mostafa <jalal.a.mostapha@gmail.com>
Cc: maciej.fijalkowski@intel.com, netdev@vger.kernel.org,
bpf@vger.kernel.org, bjorn@kernel.org, magnus.karlsson@intel.com,
jonathan.lemon@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
daniel@iogearbox.net, john.fastabend@gmail.com, hawk@kernel.org,
ast@kernel.org, linux-kernel@vger.kernel.org,
jalal.mostafa@kit.edu
Subject: Re: [PATCH bpf v3] xsk: inherit need_wakeup flag for shared sockets
Date: Thu, 22 Sep 2022 15:20:14 +0000 [thread overview]
Message-ID: <166386001443.15287.1242641673670233629.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220921135701.10199-1-jalal.a.mostapha@gmail.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 21 Sep 2022 13:57:01 +0000 you wrote:
> The flag for need_wakeup is not set for xsks with `XDP_SHARED_UMEM`
> flag and of different queue ids and/or devices. They should inherit
> the flag from the first socket buffer pool since no flags can be
> specified once `XDP_SHARED_UMEM` is specified.
>
> Fixes: b5aea28dca134 ("xsk: Add shared umem support between queue ids")
>
> [...]
Here is the summary with links:
- [bpf,v3] xsk: inherit need_wakeup flag for shared sockets
https://git.kernel.org/bpf/bpf/c/60240bc26114
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:[~2022-09-22 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 11:58 [PATCH bpf v2] xsk: inherit need_wakeup flag for shared sockets Jalal Mostafa
2022-09-20 13:34 ` Magnus Karlsson
2022-09-21 12:16 ` Maciej Fijalkowski
2022-09-21 13:57 ` [PATCH bpf v3] " Jalal Mostafa
2022-09-22 15:20 ` 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=166386001443.15287.1242641673670233629.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=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=jalal.a.mostapha@gmail.com \
--cc=jalal.mostafa@kit.edu \
--cc=john.fastabend@gmail.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--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).