qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Christoph Hellwig <public-hch-jcswGhMUV9g@plane.gmane.org>
Cc: public-kwolf-H+wXaHxf7aLQT0dZR+AlfA@plane.gmane.org,
	public-sheepdog-CJ+3F33aHDCwRfvgX43A7Q@plane.gmane.org,
	Stefan Hajnoczi
	<public-stefanha-Re5JQEeQqe8AvxtiuMwx3w@plane.gmane.org>,
	public-qemu-devel-qX2TKyscuCcdnm+yROfE0A@plane.gmane.org
Subject: Re: [Qemu-devel] coroutine bug?, was Re: [PATCH] sheepdog: use coroutines
Date: Wed, 04 Jan 2012 18:03:30 +0100	[thread overview]
Message-ID: <4F048662.1020702@redhat.com> (raw)
In-Reply-To: <20120104155825.GA11210@lst.de>



On 01/04/2012 04:58 PM, Christoph Hellwig wrote:
> Btw, what is the plan forward for the block I/O interface?  Only
> qcow2, sheepdog and nbd implement the coroutine interfaces

Actually all formats implement a coroutine interface except raw, qed and 
vdi (IIRC).  But the "minor" formats do not implement scatter/gather 
I/O, and use a bounce buffer instead.

Among the protocols, only nbd implements coroutines, the others use AIO.

> , and none of the
> hardware emulations calls them directly.

Yes, AIO is often simpler to use for hardware emulation (or anyway it 
has smaller advantages).  But I do expect that SD could easily switch 
from synchronous to coroutines, for example.  Floppy is a mess.

IMO both coroutines and AIO have their uses.  Converting qed to 
coroutines would make sense, but this is much less true for converting 
raw and even less for rbd or iscsi (the external libraries are 
callback-based).

On the other hand, changing all formats to support scatter/gather I/O 
should not be hard, and would enable some nice simplifications in the 
code.  I have enough other cleanups on my plate, though. :/

Paolo

      reply	other threads:[~2012-01-04 17:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 12:33 [Qemu-devel] [PATCH] sheepdog: use coroutines MORITA Kazutaka
2011-08-23 12:29 ` Kevin Wolf
2011-08-23 17:14   ` MORITA Kazutaka
2011-08-24 12:56     ` Kevin Wolf
2011-12-23 13:38 ` Christoph Hellwig
2011-12-29 12:06   ` [Qemu-devel] coroutine bug?, was " Christoph Hellwig
2011-12-30 10:35     ` Stefan Hajnoczi
2012-01-02 15:39       ` Christoph Hellwig
2012-01-02 15:40         ` Christoph Hellwig
2012-01-02 22:38         ` Stefan Hajnoczi
2012-01-03  8:13           ` Stefan Hajnoczi
2012-01-06 11:16             ` MORITA Kazutaka
2012-01-03  8:16         ` Stefan Hajnoczi
2012-01-04 15:58           ` Christoph Hellwig
2012-01-04 17:03             ` 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=4F048662.1020702@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=public-hch-jcswGhMUV9g@plane.gmane.org \
    --cc=public-kwolf-H+wXaHxf7aLQT0dZR+AlfA@plane.gmane.org \
    --cc=public-qemu-devel-qX2TKyscuCcdnm+yROfE0A@plane.gmane.org \
    --cc=public-sheepdog-CJ+3F33aHDCwRfvgX43A7Q@plane.gmane.org \
    --cc=public-stefanha-Re5JQEeQqe8AvxtiuMwx3w@plane.gmane.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).