From: Stefan Hajnoczi <stefanha@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
xiawenc@linux.vnet.ibm.com, qemu-devel@nongnu.org,
Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] rfifolock: add recursive FIFO lock
Date: Wed, 9 Oct 2013 13:26:09 +0200 [thread overview]
Message-ID: <20131009112609.GA29850@stefanha-thinkpad.muc.redhat.com> (raw)
In-Reply-To: <52552A77.7030504@redhat.com>
On Wed, Oct 09, 2013 at 12:05:43PM +0200, Paolo Bonzini wrote:
> Il 09/10/2013 11:55, Stefan Hajnoczi ha scritto:
> > + /* Take a ticket */
> > + unsigned int ticket = r->tail++;
> > +
> > + if (r->nesting > 0) {
> > + if (qemu_thread_is_self(&r->owner_thread)) {
> > + r->tail--; /* put ticket back, we're nesting */
> > + } else {
>
> ticket is dead in the "nested" path, why not move it (and the increment)
> directly after the else?
The increment cannot be moved because there are 3 cases:
1. Uncontended lock: r->tail++
2. Recursive lock: do not change tail
3. Wait for contended lock: r->tail++
Case #1 needs r->tail++ too.
I find this approach clearest:
if (r->nesting == 0) {
/* Uncontended, just take a ticket */
r->tail++;
} else if (qemu_thread_is_self(&r->owner_thread)) {
/* Recursive lock, no need to take a ticket */
} else {
/* Contended case, take a ticket and wait for it */
unsigned int ticket = r->tail++;
while (ticket != r->head) {
...
}
}
There's also a shorter approach which collapses everything into a single
if statement, but I find the if expression a harder to understand:
if (r->nesting == 0 || !qemu_thread_is_self(&r->owner_thread)) {
unsigned int ticket = r->tail++;
while (ticket != r->head) {
...
}
}
Any preferences?
Stefan
next prev parent reply other threads:[~2013-10-09 11:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 9:55 [Qemu-devel] [PATCH 0/2] aio: add aio_context_acquire() and aio_context_release() Stefan Hajnoczi
2013-10-09 9:55 ` [Qemu-devel] [PATCH 1/2] rfifolock: add recursive FIFO lock Stefan Hajnoczi
2013-10-09 10:05 ` Paolo Bonzini
2013-10-09 11:26 ` Stefan Hajnoczi [this message]
2013-10-09 11:36 ` Paolo Bonzini
2013-10-11 8:55 ` Wenchao Xia
2013-10-11 13:35 ` Stefan Hajnoczi
2013-10-12 2:48 ` Wenchao Xia
2013-10-09 9:55 ` [Qemu-devel] [PATCH 2/2] aio: add aio_context_acquire() and aio_context_release() Stefan Hajnoczi
2013-10-11 8:52 ` Wenchao Xia
2013-10-09 10:16 ` [Qemu-devel] [PATCH 0/2] " Paolo Bonzini
2013-10-09 11:32 ` Stefan Hajnoczi
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=20131009112609.GA29850@stefanha-thinkpad.muc.redhat.com \
--to=stefanha@redhat.com \
--cc=kwolf@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiawenc@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).