netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Eric Dumazet <edumazet@google.com>
Cc: Christian Brauner <brauner@kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH 0/2] kobject: reduce uevent_sock_mutex contention
Date: Wed, 14 Feb 2024 11:27:20 +0100	[thread overview]
Message-ID: <2024021444-getaway-partly-e055@gregkh> (raw)
In-Reply-To: <20240214084829.684541-1-edumazet@google.com>

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

  parent reply	other threads:[~2024-02-14 10:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14  8:48 [PATCH 0/2] kobject: reduce uevent_sock_mutex contention Eric Dumazet
2024-02-14  8:48 ` [PATCH 1/2] kobject: make uevent_seqnum atomic Eric Dumazet
2024-02-16 14:52   ` Christian Brauner
2024-02-14  8:48 ` [PATCH 2/2] kobject: reduce uevent_sock_mutex scope Eric Dumazet
2024-02-16 14:53   ` Christian Brauner
2024-02-14 10:27 ` Greg Kroah-Hartman [this message]
2024-02-14 10:43   ` [PATCH 0/2] kobject: reduce uevent_sock_mutex contention Eric Dumazet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2024021444-getaway-partly-e055@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rafael@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).