From: Christoph Hellwig <hch@lst.de>
To: Samuel Thibault <samuel.thibault@gnu.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Christoph Hellwig <hch@lst.de>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] Do we need CONFIG_AIO?
Date: Mon, 25 May 2009 15:00:34 +0200 [thread overview]
Message-ID: <20090525130034.GA18197@lst.de> (raw)
In-Reply-To: <20090525125852.GK5909@const.bordeaux.inria.fr>
On Mon, May 25, 2009 at 02:58:52PM +0200, Samuel Thibault wrote:
> qemu on MiniOS is used to provide efficient full virtualisation, so yes
> it's performance sensitive, but for performances we use a block-vbd
> interface. Keeping the block-posix interface for non-performance
> critical resources that can not go through vbd is still important, so we
> need to be able to compile it.
Apparently all this is not in upstream qemu, right? I really don't see
the reason to keep all this stuff around for out of tree bits only
given it is a significant burden.
next prev parent reply other threads:[~2009-05-25 13:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 8:21 [Qemu-devel] Do we need CONFIG_AIO? Christoph Hellwig
2009-05-25 11:49 ` Stefano Stabellini
2009-05-25 12:29 ` Christoph Hellwig
2009-05-25 12:58 ` Samuel Thibault
2009-05-25 13:00 ` Christoph Hellwig [this message]
2009-05-25 13:26 ` Stefano Stabellini
2009-05-25 13:35 ` Todd T. Fries
2009-05-25 13:40 ` Christoph Hellwig
2009-05-25 13:47 ` Avi Kivity
2009-05-25 15:24 ` Todd T. Fries
2009-05-25 15:27 ` Avi Kivity
2009-05-26 7:58 ` Anthony Liguori
2009-05-26 8:19 ` Christoph Hellwig
2009-05-26 10:02 ` Stefano Stabellini
2009-05-26 13:25 ` Anthony Liguori
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=20090525130034.GA18197@lst.de \
--to=hch@lst.de \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@gnu.org \
--cc=stefano.stabellini@eu.citrix.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 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).