Message ID | 20240214084829.684541-1-edumazet@google.com (mailing list archive) |
---|---|
Headers | show |
Series | kobject: reduce uevent_sock_mutex contention | expand |
On Wed, Feb 14, 2024 at 08:48:27AM +0000, Eric Dumazet wrote: > This series reduces the (small ?) contention over uevent_sock_mutex, > noticed when creating/deleting many network namespaces/devices. > > 1) uevent_seqnum becomes an atomic64_t > > 2) Only acquire uevent_sock_mutex whenever using uevent_sock_list Cool, any boot-time measured speedups from this? Or is this just tiny optimizations that you noticed doing reviews? thanks, greg k-h
On Wed, Feb 14, 2024 at 11:34 AM Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote: > > On Wed, Feb 14, 2024 at 08:48:27AM +0000, Eric Dumazet wrote: > > This series reduces the (small ?) contention over uevent_sock_mutex, > > noticed when creating/deleting many network namespaces/devices. > > > > 1) uevent_seqnum becomes an atomic64_t > > > > 2) Only acquire uevent_sock_mutex whenever using uevent_sock_list > > Cool, any boot-time measured speedups from this? Or is this just tiny > optimizations that you noticed doing reviews? No impressive nice numbers yet, the main bottleneck is still rtnl, which I am working on net-next tree. Other candidates are : rdma_nets_rwsem, proc_subdir_lock, pcpu_alloc_mutex, ... Christian made the much needed changes [1], since the last time I took a look at kobject (this was in 2017 !) [1] commit a3498436b3a0f8ec289e6847e1de40b4123e1639 Author: Christian Brauner <brauner@kernel.org> Date: Sun Apr 29 12:44:12 2018 +0200 netns: restrict uevents