From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrei Vagin <avagin@openvz.org>
Cc: <netdev@vger.kernel.org>
Subject: random thoughts on optmizing network namespace exit.
Date: Wed, 23 Nov 2016 17:52:48 -0600 [thread overview]
Message-ID: <87eg21ycrz.fsf@xmission.com> (raw)
Fundamentally if we want things to get better we have to remove
unnecessary serialization. It is entirely too easy to sleep when
cleaning up a networking subsystem and create long hold times on
net_mutex for no particular reasons.
What probably makes sense to do is to add the concept of a
non-serialized pernet_operation. And then work through the networking
stack converting all of the pernet_operations. That should allow
network namespace exits to overlap while they clean up, and it should
allow the net_mutex to be dropped at the same point we drop rtnl_lock
in cleanup_net.
It might be a touch tricky during the transition period to take
advantage of an early drop of net_mutex, but that is where I would
start.
Once net_mutex is no longer used to serialize initialization/cleanup
methods for a network namespace. We can look at other bottlenecks.
Eric
reply other threads:[~2016-11-23 23:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87eg21ycrz.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=avagin@openvz.org \
--cc=netdev@vger.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