From: Tim Chen <tim.c.chen@linux.intel.com>
To: Davidlohr Bueso <davidlohr.bueso@hp.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Alex Shi <alex.shi@intel.com>, Andi Kleen <andi@firstfloor.org>,
Michel Lespinasse <walken@google.com>,
Matthew R Wilcox <matthew.r.wilcox@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Rik van Riel <riel@redhat.com>,
Peter Hurley <peter@hurleysoftware.com>,
linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH v4 5/5] rwsem: do optimistic spinning for writer lock acquisition
Date: Wed, 26 Jun 2013 15:56:37 -0700 [thread overview]
Message-ID: <1372287397.22432.146.camel@schen9-DESK> (raw)
In-Reply-To: <1372286407.3954.6.camel@buesod1.americas.hpqcorp.net>
On Wed, 2013-06-26 at 15:40 -0700, Davidlohr Bueso wrote:
> On Wed, 2013-06-26 at 15:28 -0700, Tim Chen wrote:
> > We want to add optimistic spinning to rwsems because we've noticed that
> > the writer rwsem does not perform as well as mutexes. Tim noticed that
> > for exim (mail server) workloads, when reverting commit 4fc3f1d6 and Davidlohr
> > noticed it when converting the i_mmap_mutex to a rwsem in some aim7
> > workloads. We've noticed that the biggest difference, in a nutshell, is
> > when we fail to acquire a mutex in the fastpath, optimistic spinning
> > comes in to play and we can avoid a large amount of unnecessary sleeping
> > and wait queue overhead.
> >
> > For rwsems on the other hand, upon entering the writer slowpath in
> > rwsem_down_write_failed(), we just acquire the ->wait_lock, add
> > ourselves to the wait_queue and blocking until we get the lock.
> >
> > Reviewed-by: Peter Zijlstra <peterz@infradead.org>
> > Reviewed-by: Peter Hurley <peter@hurleysoftware.com>
> > Signed-off-by: Tim Chen <tim.c.chen@linux.intel.com>
> > Signed-off-by: Davidlohr Bueso <davidlohr.bueso@hp.com>
> > ---
> > include/linux/rwsem.h | 3 +
> > init/Kconfig | 9 +++
> > kernel/rwsem.c | 29 +++++++++-
> > lib/rwsem.c | 150 +++++++++++++++++++++++++++++++++++++++++++++----
> > 4 files changed, 179 insertions(+), 12 deletions(-)
> >
> > diff --git a/include/linux/rwsem.h b/include/linux/rwsem.h
> > index 0616ffe..0c5933b 100644
> > --- a/include/linux/rwsem.h
> > +++ b/include/linux/rwsem.h
> > @@ -29,6 +29,9 @@ struct rw_semaphore {
> > #ifdef CONFIG_DEBUG_LOCK_ALLOC
> > struct lockdep_map dep_map;
> > #endif
> > +#ifdef CONFIG_RWSEM_SPIN_ON_WRITE_OWNER
> > + struct task_struct *owner;
> > +#endif
> > };
> >
> > extern struct rw_semaphore *rwsem_down_read_failed(struct rw_semaphore *sem);
> > diff --git a/init/Kconfig b/init/Kconfig
> > index 9d3a788..1c582d1 100644
> > --- a/init/Kconfig
> > +++ b/init/Kconfig
> > @@ -1595,6 +1595,15 @@ config TRACEPOINTS
> >
> > source "arch/Kconfig"
> >
> > +config RWSEM_SPIN_ON_WRITE_OWNER
> > + bool "Optimistic spin write acquisition for writer owned rw-sem"
> > + default n
> > + depends on SMP
> > + help
> > + Allows a writer to perform optimistic spinning if another writer own
> > + the read write semaphore. This gives a greater chance for writer to
> > + acquire a semaphore before blocking it and putting it to sleep.
> > +
>
> Quoting from kernel/mutex.c:
>
> "The rationale is that if the lock owner is running, it is likely to
> release the lock soon."
>
> It would be good to add that to the Kconfig.
Sounds good.
Tim
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2013-06-26 22:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1372282738.git.tim.c.chen@linux.intel.com>
2013-06-26 22:27 ` [PATCH v4 1/5] rwsem: check the lock before cpmxchg in down_write_trylock Tim Chen
2013-06-27 1:32 ` Alex Shi
2013-06-27 15:59 ` Tim Chen
2013-06-26 22:27 ` [PATCH v4 2/5] rwsem: remove 'out' label in do_wake Tim Chen
2013-06-26 22:28 ` [PATCH v4 3/5] rwsem: remove try_reader_grant label do_wake Tim Chen
2013-06-26 22:28 ` [PATCH v4 4/5] rwsem/wake: check lock before do atomic update Tim Chen
2013-06-26 22:28 ` [PATCH v4 5/5] rwsem: do optimistic spinning for writer lock acquisition Tim Chen
2013-06-26 22:40 ` Davidlohr Bueso
2013-06-26 22:56 ` Tim Chen [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=1372287397.22432.146.camel@schen9-DESK \
--to=tim.c.chen@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@intel.com \
--cc=andi@firstfloor.org \
--cc=dave.hansen@intel.com \
--cc=davidlohr.bueso@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.r.wilcox@intel.com \
--cc=mingo@elte.hu \
--cc=peter@hurleysoftware.com \
--cc=riel@redhat.com \
--cc=walken@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