qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gautham R Shenoy <ego@in.ibm.com>
To: Qemu-development List <qemu-devel@nongnu.org>
Cc: Anthony Liguori <aliguori@linux.vnet.ibm.com>,
	Avi Kivity <avi@redhat.com>,
	Corentin Chary <corentin.chary@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V5 0/2] Threadlets: A generic task offloading framework
Date: Fri, 9 Jul 2010 11:17:54 +0530	[thread overview]
Message-ID: <20100709054754.GA19803@in.ibm.com> (raw)
In-Reply-To: <20100622111719.25556.15644.stgit@localhost.localdomain>

Hi,

I couldn't see this in the mainline codebase.

Wondering if something else needs to be done in this patch-set.

Thanks and Regards
gautham.


On Tue, Jun 22, 2010 at 04:48:08PM +0530, Gautham R Shenoy wrote:
> Hi,
> 
> This is the v5 of the patch-series to have a generic asynchronous task
> offloading framework (called threadlets) within qemu.
> 
> V4 can be found here:
> http://lists.gnu.org/archive/html/qemu-devel/2010-06/msg02152.html
> 
> Changes from V4:
> =====================================================================
> - Updated the Makefile to make the object files depend on CONFIG_POSIX.
> 
> - Did away with the pthread_barrier_init() and pthread_barrier_wait().
> 
> - Did away with flush_threadlet_queue() helper.
> 
> - Fixed the attribution in copyright, helper names.
> 
> - Fixed the idle-thread-exit logic.
> 
> - Added documentation in docs/
> 
> Description
> =====================================================================
> This patch series decouples the asynchronous threading framework
> implementation from posix-aio-compat.c to implement a generic asynchronous
> task offloading threading framework called threadlets which can be used
> by other subsystems within QEMU.
> 
> Currently within QEMU, the AIO subsystem (paio) creates a bunch of
> asynchronous threads to offload any blocking operations so that
> the vcpu threads and the IO thread can go back to servicing any
> other guest requests.
> 
> This offloading framework can be used by subsystems such as virtio-9p,
> Asynchronous encoding for vnc-server, so that the vcpu thread can offload
> blocking operations on to the asynchronous threads and resume servicing
> any other guest requests. The asynchronous threads, after
> finishing the blocking operations can then transfer the control over
> to the IO thread so that the latter can handle the post_blocking_operation().
> 
> The patch series passed fsstress test without any issues.
> 
> Could it be considered for inclusion ?
> 
> ---
> 
> Aneesh Kumar K.V (1):
>       qemu: Generic task offloading framework: threadlets
> 
> Gautham R Shenoy (1):
>       qemu: Convert AIO code to use threadlets.
> 
> 
>  Makefile.objs          |    3 +
>  docs/async-support.txt |  141 ++++++++++++++++++++++++++++++++++++++++
>  posix-aio-compat.c     |  152 +++++++------------------------------------
>  qemu-threadlets.c      |  170 ++++++++++++++++++++++++++++++++++++++++++++++++
>  qemu-threadlets.h      |   48 ++++++++++++++
>  5 files changed, 385 insertions(+), 129 deletions(-)
>  create mode 100644 docs/async-support.txt
>  create mode 100644 qemu-threadlets.c
>  create mode 100644 qemu-threadlets.h
> 
> -- 
> Thanks and Regards
> gautham.
> 

-- 
Thanks and Regards
gautham

      parent reply	other threads:[~2010-07-09  5:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22 11:18 [Qemu-devel] [PATCH V5 0/2] Threadlets: A generic task offloading framework Gautham R Shenoy
2010-06-22 11:18 ` [Qemu-devel] [PATCH V5 1/2] qemu: Generic task offloading framework: threadlets Gautham R Shenoy
2010-06-22 13:00   ` [Qemu-devel] " Paolo Bonzini
2010-06-22 11:18 ` [Qemu-devel] [PATCH V5 2/2] qemu: Convert AIO code to use threadlets Gautham R Shenoy
2010-07-09  5:47 ` Gautham R Shenoy [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=20100709054754.GA19803@in.ibm.com \
    --to=ego@in.ibm.com \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=avi@redhat.com \
    --cc=corentin.chary@gmail.com \
    --cc=pbonzini@redhat.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).