qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Gautham R Shenoy <ego@in.ibm.com>
Cc: Anthony Liguori <aliguori@linux.vnet.ibm.com>,
	Avi Kivity <avi@redhat.com>,
	Qemu-development List <qemu-devel@nongnu.org>,
	Corentin Chary <corentin.chary@gmail.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: [Qemu-devel] Re: [PATCH V4 2/3] qemu: Generic task offloading framework: threadlets
Date: Wed, 16 Jun 2010 14:34:16 +0200	[thread overview]
Message-ID: <4C18C4C8.8090901@redhat.com> (raw)
In-Reply-To: <20100616115656.10988.96529.stgit@localhost.localdomain>

> +block-obj-y += qemu-thread.o
> +block-obj-y += async-work.o

These should be (at least for now) block-obj-$(CONFIG_POSIX).

> +        while (QTAILQ_EMPTY(&(queue->request_list))&&
> +               (ret != ETIMEDOUT)) {
> +            ret = qemu_cond_timedwait(&(queue->cond),
> +					&(queue->lock), 10*100000);
> +        }

Using qemu_cond_timedwait is a hack for not properly broadcasting the 
condvar in flush_threadlet_queue.

> +        if (QTAILQ_EMPTY(&(queue->request_list)))
> +            goto check_exit;

What's the reason for the goto?  {...} works just as well.

> +/**
> + * flush_threadlet_queue: Wait till completion of all the submitted tasks
> + * @queue: Queue containing the tasks we're waiting on.
> + */
> +void flush_threadlet_queue(ThreadletQueue *queue)
> +{
> +    qemu_mutex_lock(&queue->lock);
> +    queue->exit = 1;
> +
> +    qemu_barrier_init(&queue->barr, queue->cur_threads + 1);
> +    qemu_mutex_unlock(&queue->lock);
> +
> +    qemu_barrier_wait(&queue->barr);

Can be implemented just as well with queue->cond and a loop waiting for 
queue->cur_threads == 0.  This would remove the need to implement 
barriers in qemu-threads (especially for Win32).  Anyway whoever will 
contribute Win32 qemu-threads can do it, since it's not hard.

> +int cancel_threadlet_common(ThreadletWork *work)
> +{
> +    return cancel_threadlet(&globalqueue, work);
> +}

I would prefer *_threadlet to be the globalqueue function (and 
flush_threadlets) and queue_*_threadlet to be the special-queue 
function. I should have spoken earlier probably, but please consider 
this if there will be a v5.

> + * Generalization based on posix-aio emulation code.

No need to specify these as long as the original authors are attributed 
properly.

> +static inline void threadlet_queue_init(ThreadletQueue *queue,
> +				    int max_threads, int min_threads)
> +{
> +    queue->cur_threads  = 0;
> +    queue->idle_threads = 0;
> +    queue->exit = 0;
> +    queue->max_threads  = max_threads;
> +    queue->min_threads  = min_threads;
> +    QTAILQ_INIT(&(queue->request_list));
> +    QTAILQ_INIT(&(queue->threadlet_work_pool));
> +    qemu_mutex_init(&(queue->lock));
> +    qemu_cond_init(&(queue->cond));
> +}

No need to make this inline.

> +extern void threadlet_submit(ThreadletQueue *queue,
> +				  ThreadletWork *work);
> +
> +extern void threadlet_submit_common(ThreadletWork *work);
> +
> +extern int cancel_threadlet(ThreadletQueue *queue, ThreadletWork *work);
> +extern int cancel_threadlet_common(ThreadletWork *work);
> +
> +
> +extern void flush_threadlet_queue(ThreadletQueue *queue);
> +extern void flush_common_threadlet_queue(void);

Please make the position of the verb consistent (e.g. "submit_threadlet").

Paolo

  reply	other threads:[~2010-06-16 12:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 11:56 [Qemu-devel] [PATCH V4 0/3] qemu: Threadlets: A generic task offloading framework Gautham R Shenoy
2010-06-16 11:56 ` [Qemu-devel] [PATCH V4 1/3] qemu: Add qemu-barrier support to qemu-thread framework Gautham R Shenoy
2010-06-16 14:40   ` [Qemu-devel] " Anthony Liguori
2010-06-16 14:42     ` Paolo Bonzini
2010-06-16 11:56 ` [Qemu-devel] [PATCH V4 2/3] qemu: Generic task offloading framework: threadlets Gautham R Shenoy
2010-06-16 12:34   ` Paolo Bonzini [this message]
2010-06-16 14:22     ` [Qemu-devel] " Jamie Lokier
2010-06-16 14:27       ` Anthony Liguori
2010-06-16 14:29       ` Paolo Bonzini
2010-06-16 14:38         ` Anthony Liguori
2010-06-16 14:52           ` Paolo Bonzini
2010-06-16 15:20             ` Anthony Liguori
2010-06-16 15:47               ` Corentin Chary
2010-06-16 15:52                 ` Anthony Liguori
2010-06-16 16:06                   ` Corentin Chary
2010-06-17  9:16                     ` Gautham R Shenoy
2010-06-17  9:12               ` Gautham R Shenoy
2010-06-16 14:58           ` Jamie Lokier
2010-06-16 15:07             ` Jamie Lokier
2010-06-16 16:45               ` Paolo Bonzini
2010-06-17  8:53     ` Gautham R Shenoy
2010-06-17 10:09       ` Paolo Bonzini
2010-06-17 18:05         ` Anthony Liguori
2010-06-18  7:52           ` Paolo Bonzini
2010-06-16 11:57 ` [Qemu-devel] [PATCH V4 3/3] qemu: Convert AIO code to use threadlets Gautham R Shenoy
2010-06-16 13:09 ` [Qemu-devel] [PATCH V4 0/3] qemu: Threadlets: A generic task offloading framework Anthony Liguori
2010-06-16 13:18   ` Paolo Bonzini

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=4C18C4C8.8090901@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=avi@redhat.com \
    --cc=corentin.chary@gmail.com \
    --cc=ego@in.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /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).