From: Andrew Morton <akpm@linux-foundation.org>
To: eparis@redhat.com, linux-kernel@vger.kernel.org,
viro@zeniv.linux.org.uk, hch@infradead.org,
alan@lxorguk.ukuu.org.uk, sfr@canb.auug.org.au,
john@johnmccutchan.com, rlove@rlove.org
Subject: Re: [PATCH -V2 01/13] mutex: add atomic_dec_and_mutex_lock
Date: Tue, 28 Apr 2009 13:08:47 -0700 [thread overview]
Message-ID: <20090428130847.849478bd.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090407160601.a824da99.akpm@linux-foundation.org>
On Tue, 7 Apr 2009 16:06:01 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Fri, 27 Mar 2009 16:05:08 -0400
> Eric Paris <eparis@redhat.com> wrote:
>
> > Much like the atomic_dec_and_lock() function in which we take an hold a
> > spin_lock if we drop the atomic to 0 this function takes and holds the
> > mutex if we dec the atomic to 0.
> >
> > Signed-off-by: Eric Paris <eparis@redhat.com>
> > Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > Cc: Paul Mackerras <paulus@samba.org>
> > LKML-Reference: <20090323172417.410913479@chello.nl>
> > Signed-off-by: Ingo Molnar <mingo@elte.hu>
> > ---
> >
> > include/linux/mutex.h | 23 +++++++++++++++++++++++
> > 1 files changed, 23 insertions(+), 0 deletions(-)
> >
> > diff --git a/include/linux/mutex.h b/include/linux/mutex.h
> > index 3069ec7..93054fc 100644
> > --- a/include/linux/mutex.h
> > +++ b/include/linux/mutex.h
> > @@ -151,4 +151,27 @@ extern int __must_check mutex_lock_killable(struct mutex *lock);
> > extern int mutex_trylock(struct mutex *lock);
> > extern void mutex_unlock(struct mutex *lock);
> >
> > +/**
> > + * atomic_dec_and_mutex_lock - return holding mutex if we dec to 0
> > + * @cnt: the atomic which we are to dec
> > + * @lock: the mutex to return holding if we dec to 0
> > + *
> > + * return true and hold lock if we dec to 0, return false otherwise
> > + */
> > +static inline int atomic_dec_and_mutex_lock(atomic_t *cnt, struct mutex *lock)
> > +{
> > + /* dec if we can't possibly hit 0 */
> > + if (atomic_add_unless(cnt, -1, 1))
> > + return 0;
> > + /* we might hit 0, so take the lock */
> > + mutex_lock(lock);
> > + if (!atomic_dec_and_test(cnt)) {
> > + /* when we actually did the dec, we didn't hit 0 */
> > + mutex_unlock(lock);
> > + return 0;
> > + }
> > + /* we hit 0, and we hold the lock */
> > + return 1;
> > +}
> > +
>
> This looks too large to be inlined?
It still looks too large to be inlined.
Take a look at atomic_add_unless(), and split your sides laughing.
Once you factor in all the lockdep and other debug goop, the code
generation here is pretty bewildering, but it won't be small.
prev parent reply other threads:[~2009-04-28 20:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 20:05 [PATCH -V2 01/13] mutex: add atomic_dec_and_mutex_lock Eric Paris
2009-03-27 20:05 ` [PATCH -V2 02/13] fsnotify: unified filesystem notification backend Eric Paris
2009-04-07 23:05 ` Andrew Morton
2009-04-08 0:37 ` Eric Paris
2009-04-07 23:06 ` Andrew Morton
2009-03-27 20:05 ` [PATCH -V2 03/13] fsnotify: add group priorities Eric Paris
2009-04-07 23:06 ` Andrew Morton
2009-03-27 20:05 ` [PATCH -V2 04/13] fsnotify: add in inode fsnotify markings Eric Paris
2009-04-07 23:06 ` Andrew Morton
2009-03-27 20:05 ` [PATCH -V2 05/13] fsnotify: parent event notification Eric Paris
2009-04-07 23:06 ` Andrew Morton
2009-03-27 20:05 ` [PATCH -V2 06/13] dnotify: reimplement dnotify using fsnotify Eric Paris
2009-04-07 23:06 ` Andrew Morton
2009-03-27 20:05 ` [PATCH -V2 07/13] fsnotify: generic notification queue and waitq Eric Paris
2009-04-07 23:06 ` Andrew Morton
2009-03-27 20:05 ` [PATCH -V2 08/13] fsnotify: include pathnames with entries when possible Eric Paris
2009-03-27 20:05 ` [PATCH -V2 09/13] fsnotify: add correlations between events Eric Paris
2009-04-07 23:06 ` Andrew Morton
2009-03-27 20:06 ` [PATCH -V2 10/13] fsnotify: allow groups to add private data to events Eric Paris
2009-03-27 20:06 ` [PATCH -V2 11/13] fsnotify: fsnotify marks on inodes pin them in core Eric Paris
2009-03-27 20:06 ` [PATCH -V2 12/13] fsnotify: handle filesystem unmounts with fsnotify marks Eric Paris
2009-04-07 23:06 ` Andrew Morton
2009-03-27 20:06 ` [PATCH -V2 13/13] inotify: reimplement inotify using fsnotify Eric Paris
2009-04-07 23:06 ` Andrew Morton
2009-04-07 23:06 ` [PATCH -V2 01/13] mutex: add atomic_dec_and_mutex_lock Andrew Morton
2009-04-28 20:08 ` Andrew Morton [this message]
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=20090428130847.849478bd.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=eparis@redhat.com \
--cc=hch@infradead.org \
--cc=john@johnmccutchan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlove@rlove.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.