netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: Stephen Hemminger <shemming@brocade.com>
Cc: "Eric W . Biederman" <ebiederm@xmission.com>, netdev@vger.kernel.org
Subject: [iproute PATCH 0/2] Netns performance improvements
Date: Tue,  5 Jul 2016 16:42:51 +0200	[thread overview]
Message-ID: <1467729773-16751-1-git-send-email-phil@nwl.cc> (raw)

Stress-testing OpenStack Neutron revealed poor performance of 'ip netns'
when dealing with a high amount of namespaces. The cause of this lies in
the combination of how iproute2 mounts NETNS_RUN_DIR and the netns files
therein and the fact that systemd makes all mount points of the system
shared.

Phil Sutter (2):
  ipnetns: Move NETNS_RUN_DIR into it's own propagation group
  ipnetns: Make netns mount points private

 ip/ipnetns.c | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

-- 
2.8.2

             reply	other threads:[~2016-07-05 14:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-05 14:42 Phil Sutter [this message]
2016-07-05 14:42 ` [iproute PATCH 1/2] ipnetns: Move NETNS_RUN_DIR into it's own propagation group Phil Sutter
2016-07-05 14:42 ` [iproute PATCH 2/2] ipnetns: Make netns mount points private Phil Sutter
2016-07-05 14:44 ` [iproute PATCH 0/2] Netns performance improvements Eric W. Biederman
2016-07-05 20:51   ` Phil Sutter
2016-07-07  4:58     ` Eric W. Biederman
2016-07-07 11:17       ` Phil Sutter
2016-07-07 12:59         ` Nicolas Dichtel
2016-07-07 15:48           ` Phil Sutter
2016-07-07 16:16             ` Rick Jones
2016-07-07 16:34               ` Eric W. Biederman
2016-07-07 17:28                 ` Rick Jones
2016-07-08  8:12                   ` Eric W. Biederman
2016-07-08 14:31                   ` Brian Haley
2016-07-08  8:01               ` Nicolas Dichtel
2016-07-08 17:18                 ` Rick Jones
2016-07-11 12:51                   ` Nicolas Dichtel
2016-07-05 14:49 ` Phil Sutter

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=1467729773-16751-1-git-send-email-phil@nwl.cc \
    --to=phil@nwl.cc \
    --cc=ebiederm@xmission.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemming@brocade.com \
    /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).