From: David Edmondson <david.edmondson@oracle.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Stefan Weil <sw@weilnetz.de>,
Max Reitz <mreitz@redhat.com>,
David Edmondson <david.edmondson@oracle.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <paolo.bonzini@redhat.com>
Subject: [PATCH v2 6/6] coroutine/rwlock: Avoid thundering herd when unlocking
Date: Tue, 9 Mar 2021 14:40:15 +0000 [thread overview]
Message-ID: <20210309144015.557477-7-david.edmondson@oracle.com> (raw)
In-Reply-To: <20210309144015.557477-1-david.edmondson@oracle.com>
Given that we know whether the queued coroutines are reader hopefuls
or writer hopefuls, avoid marking all of the queued coroutines as
runnable when unlocking, choosing instead to wake a single queued
writer or all queued readers.
Suggested-by: Paolo Bonzini <paolo.bonzini@redhat.com>
Signed-off-by: David Edmondson <david.edmondson@oracle.com>
---
util/qemu-coroutine-lock.c | 22 +++++++++-------------
1 file changed, 9 insertions(+), 13 deletions(-)
diff --git a/util/qemu-coroutine-lock.c b/util/qemu-coroutine-lock.c
index c05c143142..6e399f28c1 100644
--- a/util/qemu-coroutine-lock.c
+++ b/util/qemu-coroutine-lock.c
@@ -356,24 +356,20 @@ void qemu_co_rwlock_unlock(CoRwlock *lock)
Coroutine *self = qemu_coroutine_self();
assert(qemu_in_coroutine());
- if (!lock->reader) {
- /* The critical section started in qemu_co_rwlock_wrlock or
- * qemu_co_rwlock_upgrade.
- */
- qemu_co_queue_restart_all(&lock->wqueue);
- qemu_co_queue_restart_all(&lock->rqueue);
- } else {
+ if (lock->reader) {
self->locks_held--;
+ /* Read-side critical sections do not hold lock->mutex. */
qemu_co_mutex_lock(&lock->mutex);
lock->reader--;
assert(lock->reader >= 0);
- /* If there are no remaining readers wake one waiting writer
- * or all waiting readers.
- */
- if (!lock->reader && !qemu_co_queue_next(&lock->wqueue)) {
- qemu_co_queue_restart_all(&lock->rqueue);
- }
+ }
+
+ /* If there are no remaining readers wake one waiting writer or
+ * all waiting readers.
+ */
+ if (!lock->reader && !qemu_co_queue_next(&lock->wqueue)) {
+ qemu_co_queue_restart_all(&lock->rqueue);
}
qemu_co_mutex_unlock(&lock->mutex);
}
--
2.30.1
prev parent reply other threads:[~2021-03-09 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 14:40 [PATCH v2 0/6] coroutine rwlock downgrade fix, minor VDI changes David Edmondson
2021-03-09 14:40 ` [PATCH v2 1/6] block/vdi: When writing new bmap entry fails, don't leak the buffer David Edmondson
2021-03-09 14:40 ` [PATCH v2 2/6] block/vdi: Don't assume that blocks are larger than VdiHeader David Edmondson
2021-03-09 14:40 ` [PATCH v2 3/6] coroutine/mutex: Store the coroutine in the CoWaitRecord only once David Edmondson
2021-03-09 14:40 ` [PATCH v2 4/6] test-coroutine: Add rwlock downgrade test David Edmondson
2021-03-09 14:40 ` [PATCH v2 5/6] coroutine/rwlock: Wake writers in preference to readers David Edmondson
2021-03-09 14:40 ` David Edmondson [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=20210309144015.557477-7-david.edmondson@oracle.com \
--to=david.edmondson@oracle.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=paolo.bonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.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;
as well as URLs for NNTP newsgroup(s).