netdev - Re: [PATCH v2 bpf-next] xsk: mark napi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <165783181291.19017.2673215649469013294.git-patchwork-notify@kernel.org>
Date:   Thu, 14 Jul 2022 20:50:12 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Maciej Fijalkowski <maciej.fijalkowski@...el.com>
Cc:     bpf@...r.kernel.org, ast@...nel.org, daniel@...earbox.net,
        andrii@...nel.org, netdev@...r.kernel.org,
        magnus.karlsson@...el.com, bjorn@...nel.org, kuba@...nel.org
Subject: Re: [PATCH v2 bpf-next] xsk: mark napi_id on sendmsg()

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@...earbox.net>:

On Thu,  7 Jul 2022 15:08:42 +0200 you wrote:
> When application runs in busy poll mode and does not receive a single
> packet but only sends them, it is currently
> impossible to get into napi_busy_loop() as napi_id is only marked on Rx
> side in xsk_rcv_check(). In there, napi_id is being taken from
> xdp_rxq_info carried by xdp_buff. From Tx perspective, we do not have
> access to it. What we have handy is the xsk pool.
> 
> [...]

Here is the summary with links:
  - [v2,bpf-next] xsk: mark napi_id on sendmsg()
    https://git.kernel.org/bpf/bpf-next/c/ca2e1a627035

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html