From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: Davidlohr Bueso <davidlohr@hp.com>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Alex Shi <alex.shi@linaro.org>, Andi Kleen <andi@firstfloor.org>,
Michel Lespinasse <walken@google.com>,
Rik van Riel <riel@redhat.com>,
Peter Hurley <peter@hurleysoftware.com>,
Thomas Gleixner <tglx@linutronix.de>,
Aswin Chandramouleeswaran <aswin@hp.com>,
"Norton, Scott J" <scott.norton@hp.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] rwsem: Support optimistic spinning
Date: Tue, 29 Apr 2014 08:11:00 -0700 [thread overview]
Message-ID: <20140429151100.GC8754@linux.vnet.ibm.com> (raw)
In-Reply-To: <1398732649.2970.89.camel@schen9-DESK>
On Mon, Apr 28, 2014 at 05:50:49PM -0700, Tim Chen wrote:
> On Mon, 2014-04-28 at 16:10 -0700, Paul E. McKenney wrote:
>
> > > +#ifdef CONFIG_SMP
> > > +static inline bool rwsem_can_spin_on_owner(struct rw_semaphore *sem)
> > > +{
> > > + int retval;
> > > + struct task_struct *owner;
> > > +
> > > + rcu_read_lock();
> > > + owner = ACCESS_ONCE(sem->owner);
> >
> > OK, I'll bite...
> >
> > Why ACCESS_ONCE() instead of rcu_dereference()?
>
> We're using it as a speculative check on the sem->owner to see
> if the owner is running on the cpu. The rcu_read_lock
> is used for ensuring that the owner->on_cpu memory is
> still valid.
OK, so if we read complete garbage, all that happens is that we
lose a bit of performance? If so, I am OK with it as long as there
is a comment (which Davidlohr suggested later in this thread).
Thanx, Paul
> > (My first question was "where is the update side", but this is covered
> > by task_struct allocation and deallocation.)
>
> Tim
>
next prev parent reply other threads:[~2014-04-29 15:11 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 22:19 [PATCH] rwsem: Support optimistic spinning Davidlohr Bueso
2014-04-28 5:19 ` Davidlohr Bueso
2014-04-28 7:52 ` Peter Zijlstra
2014-04-28 17:18 ` Davidlohr Bueso
2014-04-28 22:09 ` [PATCH v2] " Davidlohr Bueso
2014-04-28 23:10 ` Paul E. McKenney
2014-04-29 0:50 ` Tim Chen
2014-04-29 3:05 ` Davidlohr Bueso
2014-04-29 15:11 ` Paul E. McKenney [this message]
2014-04-29 16:00 ` Tim Chen
2014-06-04 17:57 ` Andev
2014-06-04 19:44 ` Davidlohr Bueso
2014-04-30 8:01 ` Peter Zijlstra
2014-04-30 8:27 ` Peter Zijlstra
2014-04-30 16:17 ` Davidlohr Bueso
2014-04-30 17:50 ` Tim Chen
2014-04-30 18:04 ` Peter Zijlstra
2014-04-30 18:08 ` Tim Chen
2014-04-30 21:01 ` Tim Chen
2014-04-30 21:06 ` Davidlohr Bueso
2014-04-30 21:28 ` Tim Chen
2014-04-30 9:04 ` Peter Zijlstra
2014-04-30 16:33 ` Jason Low
2014-04-30 16:50 ` Peter Zijlstra
2014-04-30 9:14 ` Peter Zijlstra
2014-04-30 16:23 ` Davidlohr Bueso
2014-04-30 9:21 ` Peter Zijlstra
2014-04-30 16:32 ` Davidlohr Bueso
2014-04-30 16:37 ` Peter Zijlstra
2014-04-30 10:00 ` Peter Zijlstra
2014-04-30 16:42 ` Davidlohr Bueso
2014-05-01 3:21 ` [PATCH v3] " Davidlohr Bueso
2014-05-01 16:39 ` Tim Chen
2014-05-01 20:32 ` Jason Low
2014-05-02 18:24 ` [PATCH v4] " Davidlohr Bueso
2014-05-19 13:12 ` [tip:locking/core] " tip-bot for Davidlohr Bueso
2014-05-19 21:47 ` Davidlohr Bueso
2014-05-19 22:39 ` Davidlohr Bueso
2014-05-19 23:14 ` Jason Low
2014-05-20 0:27 ` Davidlohr Bueso
2014-05-20 0:54 ` [tip:locking/core] rwsem: Fix warnings for CONFIG_RWSEM_GENERIC_SPINLOCK tip-bot for Davidlohr Bueso
2014-06-05 14:32 ` [tip:locking/core] locking/rwsem: " tip-bot for Davidlohr Bueso
2014-06-05 8:38 ` [PATCH v4] rwsem: Support optimistic spinning Ingo Molnar
2014-06-05 16:03 ` Tim Chen
2014-06-05 14:32 ` [tip:locking/core] locking/rwsem: " tip-bot for Davidlohr Bueso
2014-05-14 15:01 ` [PATCH v5] rwsem: " 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=20140429151100.GC8754@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@linaro.org \
--cc=andi@firstfloor.org \
--cc=aswin@hp.com \
--cc=davidlohr@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peter@hurleysoftware.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=scott.norton@hp.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.org \
--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