| 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
| ||
|
Message-Id: <167946361892.17510.15632019270276603427.git-patchwork-notify@kernel.org>
Date: Wed, 22 Mar 2023 05:40:18 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Eric Dumazet <edumazet@...gle.com>
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
dsahern@...nel.org, netdev@...r.kernel.org, eric.dumazet@...il.com
Subject: Re: [PATCH net-next 0/3] net: remove some rcu_bh cruft
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 21 Mar 2023 04:01:12 +0000 you wrote:
> There is no point using rcu_bh variant hoping to free objects faster,
> especially hen using call_rcu() or kfree_rcu().
>
> Disabling/enabling BH has a non-zero cost, and adds distracting
> hot spots in kernel profilesm eg in ip6_xmit().
>
> Eric Dumazet (3):
> ipv6: flowlabel: do not disable BH where not needed
> neighbour: switch to standard rcu, instead of rcu_bh
> net: remove rcu_dereference_bh_rtnl()
>
> [...]
Here is the summary with links:
- [net-next,1/3] ipv6: flowlabel: do not disable BH where not needed
https://git.kernel.org/netdev/net-next/c/4c5c496a942f
- [net-next,2/3] neighbour: switch to standard rcu, instead of rcu_bh
https://git.kernel.org/netdev/net-next/c/09eed1192cec
- [net-next,3/3] net: remove rcu_dereference_bh_rtnl()
https://git.kernel.org/netdev/net-next/c/fe602c87df1b
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