qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v8 0/5] Coroutines for better asynchronous programming
Date: Wed, 27 Jul 2011 14:14:37 +0200	[thread overview]
Message-ID: <4E30012D.4020209@redhat.com> (raw)
In-Reply-To: <87tya83qc7.fsf@skywalker.in.ibm.com>

Am 27.07.2011 13:39, schrieb Aneesh Kumar K.V:
> Can you review the patch that add CoRWlock ?
> 
> http://article.gmane.org/gmane.comp.emulators.qemu/105402
> Message-id:1307382497-3737-2-git-send-email-aneesh.kumar@linux.vnet.ibm.com
> 
> commit 8c787d8b81aca1f4f7be45adb67b9e1a6dde7f1f
> Author: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> Date:   Tue May 24 22:14:04 2011 +0530
> 
>     coroutine: Add CoRwlock support
>     
>     Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>

Nice! I think I'll need this, too.

> diff --git a/qemu-coroutine-lock.c b/qemu-coroutine-lock.c
> index 5071fb8..5ecaa94 100644
> --- a/qemu-coroutine-lock.c
> +++ b/qemu-coroutine-lock.c
> @@ -115,3 +115,47 @@ void qemu_co_mutex_unlock(CoMutex *mutex)
>  
>      trace_qemu_co_mutex_unlock_return(mutex, self);
>  }
> +
> +void qemu_co_rwlock_init(CoRwlock *lock)
> +{
> +    memset(lock, 0, sizeof(*lock));
> +    qemu_co_queue_init(&lock->queue);
> +}
> +
> +void qemu_co_rwlock_rdlock(CoRwlock *lock)
> +{
> +    while (lock->writer) {
> +        qemu_co_queue_wait(&lock->queue);
> +    }
> +    lock->reader++;
> +}
> +
> +void qemu_co_rwlock_unlock(CoRwlock *lock)
> +{
> +    assert(qemu_in_coroutine());
> +    if (lock->writer) {
> +        lock->writer--;;

Please don't do arithmetics on bools, just say lock->write = false;

Also there's a double semicolon.

> +        assert(lock->writer == 0);
> +        while (!qemu_co_queue_empty(&lock->queue)) {
> +            /*
> +             * Wakeup every body. This will include some
> +             * writers too.
> +             */
> +            qemu_co_queue_next(&lock->queue);
> +        }
> +    } else {
> +        lock->reader--;
> +        assert(lock->reader >= 0);
> +        /* Wakeup only one waiting writer */
> +        qemu_co_queue_next(&lock->queue);

This is only useful if lock->reader == 0.

> +    }
> +}
> +
> +void qemu_co_rwlock_wrlock(CoRwlock *lock)
> +{
> +    while (lock->writer || lock->reader) {
> +        qemu_co_queue_wait(&lock->queue);
> +    }
> +    lock->writer++;
> +    assert(lock->writer == 1);
> +}

I wonder if we should have a mechanism that stops new readers from
taking the lock while a writer is waiting in order to avoid starvation.

Anyway, the locking itself looks correct.

Kevin

  reply	other threads:[~2011-07-27 12:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26  9:21 [Qemu-devel] [PATCH v8 0/5] Coroutines for better asynchronous programming Stefan Hajnoczi
2011-07-26  9:21 ` [Qemu-devel] [PATCH v8 1/5] coroutine: add gthread dependency Stefan Hajnoczi
2011-07-26  9:21 ` [Qemu-devel] [PATCH v8 2/5] coroutine: introduce coroutines API Stefan Hajnoczi
2011-07-26  9:21 ` [Qemu-devel] [PATCH v8 3/5] coroutine: add ucontext and win32 implementations Stefan Hajnoczi
2011-07-26  9:21 ` [Qemu-devel] [PATCH v8 4/5] coroutine: add test-coroutine automated tests Stefan Hajnoczi
2011-08-02 13:43   ` Kevin Wolf
2011-07-26  9:21 ` [Qemu-devel] [PATCH v8 5/5] coroutine: add test-coroutine --benchmark-lifecycle Stefan Hajnoczi
2011-07-26  9:23 ` [Qemu-devel] [PATCH v8 0/5] Coroutines for better asynchronous programming Stefan Hajnoczi
2011-07-27  9:45 ` Aneesh Kumar K.V
2011-07-27 10:03   ` Kevin Wolf
2011-07-27 11:39     ` Aneesh Kumar K.V
2011-07-27 12:14       ` Kevin Wolf [this message]
2011-07-27 11:34   ` Aneesh Kumar K.V
2011-07-29 12:54 ` 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=4E30012D.4020209@redhat.com \
    --to=kwolf@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=blauwirbel@gmail.com \
    --cc=jvrao@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).