From: Hugh Dickins <hughd@google.com>
To: Tejun Heo <tj@kernel.org>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Li Zefan <lizf@cn.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
Manfred Spraul <manfred@colorfullife.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Ying Han <yinghan@google.com>, Greg Thelen <gthelen@google.com>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memcg: restore ss->id_lock to spinlock, using RCU for next
Date: Thu, 19 Jan 2012 12:46:56 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.00.1201191235330.29542@eggly.anvils> (raw)
In-Reply-To: <1326979818.2249.12.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2013 bytes --]
On Thu, 19 Jan 2012, Eric Dumazet wrote:
> Le jeudi 19 janvier 2012 à 04:28 -0800, Tejun Heo a écrit :
> > Hello,
> >
> > On Wed, Jan 18, 2012 at 11:33 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> > > Interesting, but should be a patch on its own.
> >
> > Yeap, agreed.
Okay, in that case I'd better split into three (idr, revert, remove lock).
I'll send those three in a moment. I've also slipped an RCU comment from
idr_find into idr_get_next, and put the Acks in all three.
> >
> > > Maybe other idr users can benefit from your idea as well, if patch is
> > > labeled "idr: allow idr_get_next() from rcu_read_lock" or something...
> > >
> > > I suggest introducing idr_get_next_rcu() helper to make the check about
> > > rcu cleaner.
> > >
> > > idr_get_next_rcu(...)
> > > {
> > > WARN_ON_ONCE(!rcu_read_lock_held());
> > > return idr_get_next(...);
> > > }
> >
> > Hmmm... I don't know. Does having a separate set of interface help
> > much? It's easy to avoid/miss the test by using the other one. If we
> > really worry about it, maybe indicating which locking is to be used
> > during init is better? We can remember the lockdep map and trigger
> > WARN_ON_ONCE() if neither the lock or RCU read lock is held.
>
>
> There is a rcu_dereference_raw(ptr) in idr_get_next()
>
> This could be changed to rcu_dereference_check(ptr, condition) to get
> lockdep support for free :)
>
> [ condition would be the appropriate
> lockdep_is_held(&the_lock_protecting_my_idr) or 'I use the rcu variant'
> and I hold rcu_read_lock ]
>
> This would need to add a 'condition' parameter to idr_gen_next(), but we
> have very few users in kernel at this moment.
idr_get_next() was introduced for memcg, and has only one other user
user in the tree (drivers/mtd/mtdcore.c, which uses a mutex to lock it).
With the RCU fix, idr_get_next() becomes very much like idr_find().
I'll leave any fiddling with their interfaces to you guys.
Hugh
next prev parent reply other threads:[~2012-01-19 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 6:05 Hugh Dickins
2012-01-19 6:58 ` KAMEZAWA Hiroyuki
2012-01-19 7:31 ` Li Zefan
2012-01-19 7:33 ` Eric Dumazet
2012-01-19 12:28 ` Tejun Heo
2012-01-19 13:30 ` Eric Dumazet
2012-01-19 20:46 ` Hugh Dickins [this message]
2012-01-19 20:48 ` [PATCH 1/3] idr: make idr_get_next() good for rcu_read_lock() Hugh Dickins
2012-01-20 23:48 ` Andrew Morton
2012-01-21 3:45 ` Hugh Dickins
2012-01-21 20:43 ` Randy Dunlap
2012-01-19 20:50 ` [PATCH 2/3] cgroup: revert ss_id_lock to spinlock Hugh Dickins
2012-01-19 20:51 ` [PATCH 3/3] memcg: let css_get_next() rely upon rcu_read_lock() Hugh Dickins
2012-01-19 20:53 ` Tejun Heo
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=alpine.LSU.2.00.1201191235330.29542@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=eric.dumazet@gmail.com \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=manfred@colorfullife.com \
--cc=tj@kernel.org \
--cc=yinghan@google.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