| 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
| ||
|
Date: Tue, 8 Aug 2017 18:02:29 +0200
From: Florian Westphal <fw@...len.de>
To: <netdev@...r.kernel.org>
Subject: [PATCH net-next 0/7] rtnetlink: allow to run selected handlers without rtnl
The RTNL mutex is used to serialize both rtnetlink calls and dump requests.
Its also used to protect other things such as the list of current netns.
Unfortunately RTNL mutex is a performance issue, e.g. a cpu adding an
ip address prevents other cpus from seemingly unrelated tasks such as
dumping tc classifiers.
This patch set attempts to add basic infrastructure to start pushing the
rtnl lock down to those places that need it, or even elide it entirely in
some cases.
Subsystems can now indicate that their doit() callback can run without
RTNL mutex. Such callbacks can then run in parallel.
This will obviously need a lot of followup work; all current users need
to be audited/changed to benefit from this.
Initial no-rtnl spots are ip6 fib add/del and netns new/getid.
Dumps are another problem entirely, see
commit 2907c35ff64708065 ("net: hold rtnl again in dump callbacks"),
this patchset doesn't touch them.
Powered by blists - more mailing lists