All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gautham R Shenoy <ego@in.ibm.com>
To: Chris Wright <chrisw@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org,
	jvrao <jvrao@linux.vnet.ibm.com>,
	Corentin Chary <corentin.chary@gmail.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	sripathik@in.ibm.com
Subject: Re: [Qemu-devel] KVM call agenda for May 25
Date: Tue, 25 May 2010 12:26:01 +0530	[thread overview]
Message-ID: <20100525065601.GA28183@in.ibm.com> (raw)
In-Reply-To: <20100525002104.GM7635@x200.localdomain>

On Mon, May 24, 2010 at 05:21:04PM -0700, Chris Wright wrote:
> Please send in any agenda items you are interested in covering.
> 

Sorry for the delayed response.

If the community is interested, I would
like to discuss the Generic Asynchronous task offloading framework
patches posted to the community on 24th May 2010.
URL:http://lists.gnu.org/archive/html/qemu-devel/2010-05/msg02227.html

Brief Description: The patch series extracts out the task offloading
framework code from posix-aio-compat.c which is currently being used
only by the paio subsystem to create a generic task offloading framework
that could be used by other subsystems within qemu. Currently virtio-9p
and asynchronous-encoding from vnc server can make use of the generic
framework.

Points for discussion:
- Is a generic task offloading framework the way to go for subsystems
  such as virtio-9p, which would like to emulate the AIO behaviour
  that allows us to free the vcpu thread to handle any other guest requests.

- Currently the AIO helper threads indicate the completion of the task
  to the IO-thread by sending a SIGUSR2, the handler for which does a
  write() to the file descriptor on which the IO thread is waiting using
  a select. Should we use this signal-handling mechanism to communicate
  between the generic asynchronous helper threads and the IO-Thread ?


> If we have a lack of agenda items I'll cancel the week's call.
> 
> thanks,
> -chris
> 

-- 
Thanks and Regards
gautham

WARNING: multiple messages have this Message-ID (diff)
From: Gautham R Shenoy <ego@in.ibm.com>
To: Chris Wright <chrisw@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org, sripathik@in.ibm.com,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Corentin Chary <corentin.chary@gmail.com>,
	jvrao <jvrao@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] KVM call agenda for May 25
Date: Tue, 25 May 2010 12:26:01 +0530	[thread overview]
Message-ID: <20100525065601.GA28183@in.ibm.com> (raw)
In-Reply-To: <20100525002104.GM7635@x200.localdomain>

On Mon, May 24, 2010 at 05:21:04PM -0700, Chris Wright wrote:
> Please send in any agenda items you are interested in covering.
> 

Sorry for the delayed response.

If the community is interested, I would
like to discuss the Generic Asynchronous task offloading framework
patches posted to the community on 24th May 2010.
URL:http://lists.gnu.org/archive/html/qemu-devel/2010-05/msg02227.html

Brief Description: The patch series extracts out the task offloading
framework code from posix-aio-compat.c which is currently being used
only by the paio subsystem to create a generic task offloading framework
that could be used by other subsystems within qemu. Currently virtio-9p
and asynchronous-encoding from vnc server can make use of the generic
framework.

Points for discussion:
- Is a generic task offloading framework the way to go for subsystems
  such as virtio-9p, which would like to emulate the AIO behaviour
  that allows us to free the vcpu thread to handle any other guest requests.

- Currently the AIO helper threads indicate the completion of the task
  to the IO-thread by sending a SIGUSR2, the handler for which does a
  write() to the file descriptor on which the IO thread is waiting using
  a select. Should we use this signal-handling mechanism to communicate
  between the generic asynchronous helper threads and the IO-Thread ?


> If we have a lack of agenda items I'll cancel the week's call.
> 
> thanks,
> -chris
> 

-- 
Thanks and Regards
gautham

  reply	other threads:[~2010-05-25  6:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-25  0:21 KVM call agenda for May 25 Chris Wright
2010-05-25  0:21 ` [Qemu-devel] " Chris Wright
2010-05-25  6:56 ` Gautham R Shenoy [this message]
2010-05-25  6:56   ` Gautham R Shenoy

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=20100525065601.GA28183@in.ibm.com \
    --to=ego@in.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=chrisw@redhat.com \
    --cc=corentin.chary@gmail.com \
    --cc=jvrao@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sripathik@in.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 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.