From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Oleg Nesterov <oleg@redhat.com>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
der.herr@hofr.at, Davidlohr Bueso <dave@stgolabs.net>
Subject: Re: [RFC][PATCH 0/5] Optimize percpu-rwsem
Date: Tue, 26 May 2015 14:35:20 -0400 [thread overview]
Message-ID: <20150526183520.GI7099@htj.duckdns.org> (raw)
In-Reply-To: <CA+55aFwxjAWTm9XZg0ZE6kB70S8iKV6b8RQL8Bi6fapaPbwpRQ@mail.gmail.com>
Hello, Linus.
On Tue, May 26, 2015 at 11:12:04AM -0700, Linus Torvalds wrote:
...
> Is there some new use that I don't know about? Have people really
> looked at that uprobes code deeply? OF COURSE global locks will have
> problems, I'm not at all convinced that "let's make that global lock
> really complicated and clever" is the proper solution.
I've posted a patchset to make threadgroup rwsem cgroup-specific (it
is used only by cgroups) and replace the per-threadgroup rwsems with a
global percpu_rwsem. This is primarily to allow either succeeding or
failing migrations of multiple tasks atomically. We already try to do
multiple task migrations in some corner cases and the unified
hierarchy will make wider use of it. Currently, the implementation is
broken as there's no easy way of reverting changes if the operation
fails in the middle.
Given that task migrations aren't particularly high frequency
operations, a global percpu_rwsem is likely to be workable while being
less tedious and slightly less costly for the usual fork/exit paths.
That said, from cgroup's pov, write-locking per-threadgroup rwsems of
all target tasks works too although we'd need an outer mutex to
serialize down-write attempts to avoid locking order issues.
Thanks.
--
tejun
next prev parent reply other threads:[~2015-05-26 18:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 11:43 Peter Zijlstra
2015-05-26 11:43 ` [RFC][PATCH 1/5] rcu: Create rcu_sync infrastructure Peter Zijlstra
2015-05-30 16:58 ` Paul E. McKenney
2015-05-30 19:16 ` Oleg Nesterov
2015-05-30 19:25 ` Oleg Nesterov
2015-05-31 16:07 ` Paul E. McKenney
2015-05-26 11:43 ` [RFC][PATCH 2/5] rcusync: Introduce struct rcu_sync_ops Peter Zijlstra
2015-05-26 11:43 ` [RFC][PATCH 3/5] rcusync: Add the CONFIG_PROVE_RCU checks Peter Zijlstra
2015-05-26 11:44 ` [RFC][PATCH 4/5] rcusync: Introduce rcu_sync_dtor() Peter Zijlstra
2015-05-26 11:44 ` [RFC][PATCH 5/5] percpu-rwsem: Optimize readers and reduce global impact Peter Zijlstra
2015-05-29 19:45 ` Oleg Nesterov
2015-05-29 20:09 ` Oleg Nesterov
2015-05-29 20:41 ` Linus Torvalds
2015-05-30 20:49 ` Oleg Nesterov
2015-06-16 11:48 ` Peter Zijlstra
2015-05-30 17:18 ` Paul E. McKenney
2015-05-30 20:04 ` ring_buffer_attach && cond_synchronize_rcu (Was: percpu-rwsem: Optimize readers and reduce global impact) Oleg Nesterov
2015-06-16 11:08 ` Peter Zijlstra
2015-06-16 11:16 ` Peter Zijlstra
2015-06-16 19:03 ` Oleg Nesterov
2015-06-19 17:57 ` [tip:perf/urgent] perf: Fix ring_buffer_attach() RCU sync, again tip-bot for Oleg Nesterov
2015-05-26 18:12 ` [RFC][PATCH 0/5] Optimize percpu-rwsem Linus Torvalds
2015-05-26 18:34 ` Peter Zijlstra
2015-05-26 18:35 ` Tejun Heo [this message]
2015-05-26 18:42 ` Davidlohr Bueso
2015-05-26 21:57 ` Linus Torvalds
2015-05-27 9:28 ` Nicholas Mc Guire
2015-06-05 1:45 ` Al Viro
2015-06-05 21:08 ` Oleg Nesterov
2015-06-05 22:11 ` Al Viro
2015-06-05 23:36 ` Oleg Nesterov
2015-05-27 6:53 ` Peter Zijlstra
2015-05-26 18:57 ` Oleg Nesterov
2015-05-26 19:13 ` Oleg Nesterov
2015-05-26 19:29 ` Oleg Nesterov
2015-05-26 19:54 ` Davidlohr Bueso
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=20150526183520.GI7099@htj.duckdns.org \
--to=tj@kernel.org \
--cc=dave@stgolabs.net \
--cc=der.herr@hofr.at \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®