[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<171352323053.9279.11233858843436039368.git-patchwork-notify@kernel.org>
Date: Fri, 19 Apr 2024 10:40:30 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jason Xing <kerneljasonxing@...il.com>
Cc: edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
davem@...emloft.net, horms@...nel.org, netdev@...r.kernel.org,
kernelxing@...cent.com
Subject: Re: [PATCH net-next v3 0/3] locklessly protect left members in struct
rps_dev_flow
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.net>:
On Thu, 18 Apr 2024 15:36:00 +0800 you wrote:
> From: Jason Xing <kernelxing@...cent.com>
>
> Since Eric did a more complicated locklessly change to last_qtail
> member[1] in struct rps_dev_flow, the left members are easier to change
> as the same.
>
> One thing important I would like to share by qooting Eric:
> "rflow is located in rxqueue->rps_flow_table, it is thus private to current
> thread. Only one cpu can service an RX queue at a time."
> So we only pay attention to the reader in the rps_may_expire_flow() and
> writer in the set_rps_cpu(). They are in the two different contexts.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/3] net: rps: protect last_qtail with rps_input_queue_tail_save() helper
https://git.kernel.org/netdev/net-next/c/84b6823cd96b
- [net-next,v3,2/3] net: rps: protect filter locklessly
https://git.kernel.org/netdev/net-next/c/f00bf5dc8320
- [net-next,v3,3/3] net: rps: locklessly access rflow->cpu
https://git.kernel.org/netdev/net-next/c/f7b60cce8470
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