All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Avi Kivity <avi@redhat.com>,
	Qemu-development List <qemu-devel@nongnu.org>,
	Corentin Chary <corentin.chary@gmail.com>,
	Gautham R Shenoy <ego@in.ibm.com>
Subject: Re: [Qemu-devel] [PATCH V4 0/3] qemu: Threadlets: A generic task offloading framework
Date: Wed, 16 Jun 2010 15:18:42 +0200	[thread overview]
Message-ID: <4C18CF32.2080300@redhat.com> (raw)
In-Reply-To: <4C18CD1D.5040600@codemonkey.ws>

On 06/16/2010 03:09 PM, Anthony Liguori wrote:
> On 06/16/2010 06:56 AM, Gautham R Shenoy wrote:
>> Hi,
>>
>> This is the v4 of the patch-series to have a generic asynchronous task
>> offloading framework (called threadlets) within qemu.
>
> Semantically, a threadlet is identical to a QEMUBH except that a QEMUBH
> holds the qemu_mutex and a threadlet doesn't.
>
> I'd suggest naming these functions similar to QEMUBH to the point where
> it makes sense to use the same structure. Instead of the normal
> qemu_bh_schedule, I'd suggest having a qemu_bh_schedule_unlocked().

The API of threadlets is much more sensible than the one of bottom 
halves, especially with respect to allocation and possibility to use 
container_of instead of opaque.

I think it's much more sensible to keep Gautham's proposed API and long 
term change all bottom halves to use threadlets.

> Also, please introduce a short document in docs/ that gives a brief
> overview of how to use unlocked bottom halves especially focusing on the
> considerations with respect to what should and shouldn't be done in
> these functions.

This is a nice idea though.

Paolo

      reply	other threads:[~2010-06-16 13:19 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   ` [Qemu-devel] " Paolo Bonzini
2010-06-16 14:22     ` 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 [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=4C18CF32.2080300@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=anthony@codemonkey.ws \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.