From: patchwork-bot+netdevbpf@kernel.org
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, netdev@vger.kernel.org,
magnus.karlsson@intel.com, bjorn@kernel.org,
michal.kubiak@intel.com
Subject: Re: [PATCH bpf] xsk: check IFF_UP earlier in Tx path
Date: Fri, 17 Feb 2023 07:10:17 +0000 [thread overview]
Message-ID: <167661781786.4204.9196824978376893308.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230215143309.13145-1-maciej.fijalkowski@intel.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Wed, 15 Feb 2023 15:33:09 +0100 you wrote:
> Xsk Tx can be triggered via either sendmsg() or poll() syscalls. These
> two paths share a call to common function xsk_xmit() which has two
> sanity checks within. A pseudo code example to show the two paths:
>
> __xsk_sendmsg() : xsk_poll():
> if (unlikely(!xsk_is_bound(xs))) if (unlikely(!xsk_is_bound(xs)))
> return -ENXIO; return mask;
> if (unlikely(need_wait)) (...)
> return -EOPNOTSUPP; xsk_xmit()
> mark napi id
> (...)
> xsk_xmit()
>
> [...]
Here is the summary with links:
- [bpf] xsk: check IFF_UP earlier in Tx path
https://git.kernel.org/bpf/bpf/c/92a3f9895236
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:[~2023-02-17 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 14:33 [PATCH bpf] xsk: check IFF_UP earlier in Tx path Maciej Fijalkowski
2023-02-15 17:57 ` Alexander Lobakin
2023-02-17 7: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=167661781786.4204.9196824978376893308.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@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@intel.com \
--cc=michal.kubiak@intel.com \
--cc=netdev@vger.kernel.org \
/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