From mboxrd@z Thu Jan  1 00:00:00 1970
From: ebiederm@xmission.com (Eric W. Biederman)
Subject: Re: [PATCH net-next 2/2] netns: isolate seqnums to use per-netns locks
Date: Wed, 18 Apr 2018 11:55:52 -0500
Message-ID: <874lk8wj1j.fsf@xmission.com>
References: <20180418152106.18519-1-christian.brauner@ubuntu.com>
        <20180418152106.18519-3-christian.brauner@ubuntu.com>
Mime-Version: 1.0
Content-Type: text/plain
Cc: davem@davemloft.net, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org, avagin@virtuozzo.com,
        ktkhai@virtuozzo.com, serge@hallyn.com, gregkh@linuxfoundation.org
To: Christian Brauner <christian.brauner@ubuntu.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <20180418152106.18519-3-christian.brauner@ubuntu.com> (Christian
        Brauner's message of "Wed, 18 Apr 2018 17:21:06 +0200")
Sender: linux-kernel-owner@vger.kernel.org
List-Id: netdev.vger.kernel.org

Christian Brauner <christian.brauner@ubuntu.com> writes:

> Now that it's possible to have a different set of uevents in different
> network namespaces, per-network namespace uevent sequence numbers are
> introduced. This increases performance as locking is now restricted to the
> network namespace affected by the uevent rather than locking
> everything.

Numbers please.  I personally expect that the netlink mc_list issues
will swamp any benefit you get from this.

Eric