[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<175523340651.927837.5280126542856100609.git-patchwork-notify@kernel.org>
Date: Fri, 15 Aug 2025 04:50:06 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jesper Dangaard Brouer <hawk@...nel.org>
Cc: bpf@...r.kernel.org, kuba@...nel.org, dtatulea@...dia.com, ast@...nel.org,
borkmann@...earbox.net, netdev@...r.kernel.org, eric.dumazet@...il.com,
davem@...emloft.net, pabeni@...hat.com, tariqt@...dia.com, memxor@...il.com,
john.fastabend@...il.com, kernel-team@...udflare.com, yan@...udflare.com,
jbrandeburg@...udflare.com, carges@...udflare.com, arzeznik@...udflare.com
Subject: Re: [PATCH bpf] cpumap: disable page_pool direct xdp_return need
larger
scope
Hello:
This patch was applied to bpf/bpf.git (master)
by Martin KaFai Lau <martin.lau@...nel.org>:
On Thu, 14 Aug 2025 20:24:37 +0200 you wrote:
> When running an XDP bpf_prog on the remote CPU in cpumap code
> then we must disable the direct return optimization that
> xdp_return can perform for mem_type page_pool. This optimization
> assumes code is still executing under RX-NAPI of the original
> receiving CPU, which isn't true on this remote CPU.
>
> The cpumap code already disabled this via helpers
> xdp_set_return_frame_no_direct() and xdp_clear_return_frame_no_direct(),
> but the scope didn't include xdp_do_flush().
>
> [...]
Here is the summary with links:
- [bpf] cpumap: disable page_pool direct xdp_return need larger scope
https://git.kernel.org/bpf/bpf/c/7572a47ebcdf
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