[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<175764243148.2373516.17876362727543730939.git-patchwork-notify@kernel.org>
Date: Fri, 12 Sep 2025 02:00:31 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Xin Zhao <jackzxcui1989@....com>
Cc: willemdebruijn.kernel@...il.com, kerneljasonxing@...il.com,
edumazet@...gle.com, ferenc@...es.dev, davem@...emloft.net, kuba@...nel.org,
pabeni@...hat.com, horms@...nel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v12 0/2] net: af_packet: optimize retire
operation
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Mon, 8 Sep 2025 18:45:47 +0800 you wrote:
> In a system with high real-time requirements, the timeout mechanism of
> ordinary timers with jiffies granularity is insufficient to meet the
> demands for real-time performance. Meanwhile, the optimization of CPU
> usage with af_packet is quite significant. Use hrtimer instead of timer
> to help compensate for the shortcomings in real-time performance.
> In HZ=100 or HZ=250 system, the update of TP_STATUS_USER is not real-time
> enough, with fluctuations reaching over 8ms (on a system with HZ=250).
> This is unacceptable in some high real-time systems that require timely
> processing of network packets. By replacing it with hrtimer, if a timeout
> of 2ms is set, the update of TP_STATUS_USER can be stabilized to within
> 3 ms.
>
> [...]
Here is the summary with links:
- [net-next,v12,1/2] net: af_packet: remove last_kactive_blk_num field
https://git.kernel.org/netdev/net-next/c/28d2420d403a
- [net-next,v12,2/2] net: af_packet: Use hrtimer to do the retire operation
https://git.kernel.org/netdev/net-next/c/f7460d2989fa
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