From: Christoph Hellwig <hch@lst.de>
To: Avi Kivity <avi@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] native Linux AIO support revisited
Date: Fri, 21 Aug 2009 16:50:48 +0200 [thread overview]
Message-ID: <20090821145048.GB22645@lst.de> (raw)
In-Reply-To: <4A8E4F87.6070405@redhat.com>
On Fri, Aug 21, 2009 at 10:40:55AM +0300, Avi Kivity wrote:
> On 08/20/2009 05:58 PM, Christoph Hellwig wrote:
> >Based on this I would recommend to include this patch, but not use it by
> >default for now. After some testing I would suggest to enable it by
> >default for host devices and investigate a way to make it easily usable
> >for files, possibly including some kernel support to tell us which files
> >are "safe".
> >
>
> I like both the numbers and the patches. But why disable by default?
> Enabling for cache=none host devices only seems a safe choice.
I want to
a) get some more testing. Especially from people who are better at
testing than me and have a wider variety of hardware
b) sort out the queue depth issue. Which I'd really prefer to once
the basic patch is in I don't have to work with a large patch
stack.
next prev parent reply other threads:[~2009-08-21 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 14:58 [Qemu-devel] [PATCH 0/2] native Linux AIO support revisited Christoph Hellwig
2009-08-20 14:58 ` [Qemu-devel] [PATCH 1/2] raw-posix: refactor AIO support Christoph Hellwig
2009-08-20 14:58 ` [Qemu-devel] [PATCH 2/2] raw-posix: add Linux native " Christoph Hellwig
2009-08-21 9:53 ` Avi Kivity
2009-08-21 14:48 ` Christoph Hellwig
2009-08-21 15:35 ` Avi Kivity
2009-08-20 19:06 ` [Qemu-devel] [PATCH 0/2] native Linux AIO support revisited Jamie Lokier
2009-08-21 7:40 ` Avi Kivity
2009-08-21 14:50 ` Christoph Hellwig [this message]
2009-08-21 15:38 ` Avi Kivity
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=20090821145048.GB22645@lst.de \
--to=hch@lst.de \
--cc=avi@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).