From: Peter Zijlstra <peterz@infradead.org>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: mingo@kernel.org, tglx@linutronix.de, Waiman.Long@hpe.com,
jason.low2@hp.com, linux-kernel@vger.kernel.org,
Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH 3/4] locking/rwsem: Enable lockless waiter wakeup(s)
Date: Mon, 9 May 2016 09:48:30 +0200 [thread overview]
Message-ID: <20160509074830.GD3430@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1462769770-29363-4-git-send-email-dave@stgolabs.net>
On Sun, May 08, 2016 at 09:56:09PM -0700, Davidlohr Bueso wrote:
> @@ -129,12 +133,14 @@ __rwsem_do_wake(struct rw_semaphore *sem, enum rwsem_wake_type wake_type)
> waiter = list_entry(sem->wait_list.next, struct rwsem_waiter, list);
> if (waiter->type == RWSEM_WAITING_FOR_WRITE) {
> if (wake_type == RWSEM_WAKE_ANY)
> - /* Wake writer at the front of the queue, but do not
> - * grant it the lock yet as we want other writers
> - * to be able to steal it. Readers, on the other hand,
> - * will block as they will notice the queued writer.
> + /*
> + * Mark writer at the front of the queue for wakeup.
> + * Until the task is actually later awoken later by
> + * the caller, other writers are able to steal it the
> + * lock to be able to steal it. Readers, on the other,
> + * hand, will block as they will notice the queued writer.
> */
> - wake_up_process(waiter->task);
> + wake_q_add(wake_q, waiter->task);
Thanks for fixing that comment; that bugged the hell out of me ;-)
> goto out;
> }
>
> @@ -196,12 +202,11 @@ __rwsem_do_wake(struct rw_semaphore *sem, enum rwsem_wake_type wake_type)
> */
> smp_mb();
> waiter->task = NULL;
> - wake_up_process(tsk);
> + wake_q_add(wake_q, tsk);
However, note that per the race in the previous email; this is too late
to acquire the tsk refcount. I think it'll work if you do wake_q_add()
_before_ the waiter->task = NULL.
On that same note; I think that you can replace:
smp_mb();
waiter->task = NULL;
with:
smp_store_release(&waiter->task, NULL);
> } while (--loop);
>
> sem->wait_list.next = next;
> next->prev = &sem->wait_list;
next prev parent reply other threads:[~2016-05-09 7:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 4:56 [PATCH -tip 0/4] locking/rwsem (xadd): Reader waiter optimizations Davidlohr Bueso
2016-05-09 4:56 ` [PATCH 1/4] locking/rwsem: Avoid stale ->count for rwsem_down_write_failed() Davidlohr Bueso
2016-05-09 5:36 ` Peter Hurley
2016-05-09 7:12 ` Peter Zijlstra
2016-05-09 14:29 ` Davidlohr Bueso
2016-05-09 4:56 ` [PATCH 2/4] locking/rwsem: Drop superfluous waiter refcount Davidlohr Bueso
2016-05-09 7:39 ` Peter Zijlstra
2016-05-09 15:56 ` Davidlohr Bueso
2016-05-09 16:11 ` Peter Zijlstra
2016-05-09 18:51 ` Davidlohr Bueso
2016-05-09 18:59 ` Peter Zijlstra
2016-05-09 4:56 ` [PATCH 3/4] locking/rwsem: Enable lockless waiter wakeup(s) Davidlohr Bueso
2016-05-09 7:48 ` Peter Zijlstra [this message]
2016-05-09 4:56 ` [PATCH 4/4] locking/rwsem: Rework zeroing reader waiter->task Davidlohr Bueso
2016-05-09 7:50 ` Peter Zijlstra
2016-05-10 1:31 ` [PATCH -tip 0/4] locking/rwsem (xadd): Reader waiter optimizations Waiman Long
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=20160509074830.GD3430@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Waiman.Long@hpe.com \
--cc=dave@stgolabs.net \
--cc=dbueso@suse.de \
--cc=jason.low2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome