From: Peter Zijlstra <peterz@infradead.org>
To: Waiman Long <waiman.long@hpe.com>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Scott J Norton <scott.norton@hpe.com>,
Douglas Hatch <doug.hatch@hpe.com>,
Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH] locking/qrwlock: Allow multiple spinning readers
Date: Fri, 1 Apr 2016 12:29:30 +0200 [thread overview]
Message-ID: <20160401102930.GI3448@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <56FDA0D6.4090904@hpe.com>
On Thu, Mar 31, 2016 at 06:12:38PM -0400, Waiman Long wrote:
> On 03/29/2016 04:20 PM, Peter Zijlstra wrote:
> >> cnts = atomic_add_return_acquire(_QR_BIAS,&lock->cnts) - _QR_BIAS;
> >>+ while ((cnts& _QW_WMASK) == _QW_LOCKED) {
> >>+ if (locked&& ((cnts>> _QR_SHIFT)< MAX_SPINNING_READERS)) {
> >>+ /*
> >>+ * Unlock the wait queue so that more readers can
> >>+ * come forward and waiting for the writer to exit
> >>+ * as long as no more than MAX_SPINNING_READERS
> >>+ * readers are present.
> >>+ */
> >>+ arch_spin_unlock(&lock->wait_lock);
> >>+ locked = false;
> >Only 1 more can come forward with this logic. How can you ever get to 4?
>
> Yes, each reader in the unlock path will release one in the queue. If the
> next one is also a reader, it will release one more and so on until the
> reader count reach 4 where the process will stop.
>
> >
> >Also, what says the next in queue is a reader?
>
> I did say in the changelog that the queue head could be a writer. In that
> case, the process will stop and the writer will wait until all the readers
> are gone.
Clearly I could not read not think straight when I looked at this patch.
You're right.
I'll go have another look ..
next prev parent reply other threads:[~2016-04-01 10:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 3:21 [PATCH] locking/qrwlock: Allow multiple spinning readers Waiman Long
2016-03-20 10:43 ` Peter Zijlstra
2016-03-22 2:21 ` Waiman Long
2016-03-29 20:20 ` Peter Zijlstra
2016-03-31 22:12 ` Waiman Long
2016-04-01 10:29 ` Peter Zijlstra [this message]
2016-04-01 10:31 ` Peter Zijlstra
2016-04-01 10:41 ` Will Deacon
2016-04-01 10:54 ` Peter Zijlstra
2016-04-01 11:43 ` Peter Zijlstra
2016-04-01 16:47 ` Will Deacon
2016-04-01 19:53 ` Peter Zijlstra
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=20160401102930.GI3448@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=doug.hatch@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=scott.norton@hpe.com \
--cc=waiman.long@hpe.com \
--cc=will.deacon@arm.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