[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<172606622953.943906.17362698555849146465.git-patchwork-notify@kernel.org>
Date: Wed, 11 Sep 2024 14:50:29 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Daniel Xu <dxu@...uu.xyz>
Cc: davem@...emloft.net, ast@...nel.org, hawk@...nel.org, kuba@...nel.org,
daniel@...earbox.net, john.fastabend@...il.com, andrii@...nel.org,
martin.lau@...ux.dev, eddyz87@...il.com, song@...nel.org,
yonghong.song@...ux.dev, kpsingh@...nel.org, sdf@...ichev.me,
haoluo@...gle.com, jolsa@...nel.org, netdev@...r.kernel.org,
bpf@...r.kernel.org, linux-kernel@...r.kernel.org, lorenzo@...nel.org,
aleksander.lobakin@...el.com, kernel-team@...a.com
Subject: Re: [PATCH bpf-next] bpf: cpumap: Move xdp:xdp_cpumap_kthread tracepoint
before rcv
Hello:
This patch was applied to bpf/bpf-next.git (net)
by Daniel Borkmann <daniel@...earbox.net>:
On Thu, 5 Sep 2024 19:22:44 -0600 you wrote:
> cpumap takes RX processing out of softirq and onto a separate kthread.
> Since the kthread needs to be scheduled in order to run (versus softirq
> which does not), we can theoretically experience extra latency if the
> system is under load and the scheduler is being unfair to us.
>
> Moving the tracepoint to before passing the skb list up the stack allows
> users to more accurately measure enqueue/dequeue latency introduced by
> cpumap via xdp:xdp_cpumap_enqueue and xdp:xdp_cpumap_kthread tracepoints.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: cpumap: Move xdp:xdp_cpumap_kthread tracepoint before rcv
https://git.kernel.org/bpf/bpf-next/c/23dc9867329c
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