qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: qemu-devel@nongnu.org
Cc: Christoph Hellwig <hch@infradead.org>,
	Avi Kivity <avi@redhat.com>,
	kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH][RFC] Linux AIO support when using O_DIRECT
Date: Mon, 23 Mar 2009 19:48:27 +0100	[thread overview]
Message-ID: <20090323184827.GA14826@lst.de> (raw)
In-Reply-To: <49C7D096.3000302@codemonkey.ws>

On Mon, Mar 23, 2009 at 01:10:30PM -0500, Anthony Liguori wrote:
> I really dislike having so many APIs.  I'd rather have an aio API that 
> took byte accesses or have pread/pwrite always be emulated with a full 
> sector read/write

I had patches to change the aio API to byte based access, and get rid
of the read/write methods to only have the byte based pread/pwrite
APIs, but thay got obsoleted by Avi's patch to kill the pread/pwrite
ops.  We could put in byte-based AIO without byte-based read/write,
though.  In my patches I put a flag into BlockDriverState whether we
allow byte-based access to this instance or otherwise emulated it in
the block layer.  We still need this as many of the image formats can't
deal with byte-granularity access without read-modify-write cycles,
and I think we're better off having one read-modify-write handler in
the block handler than one per image format that needs it.

  reply	other threads:[~2009-03-23 18:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23 15:45 [Qemu-devel] [PATCH][RFC] Linux AIO support when using O_DIRECT Anthony Liguori
2009-03-23 16:17 ` Avi Kivity
2009-03-23 17:14   ` Anthony Liguori
2009-03-23 17:29     ` Christoph Hellwig
2009-03-23 18:10       ` Anthony Liguori
2009-03-23 18:48         ` Christoph Hellwig [this message]
2009-03-23 19:35           ` Avi Kivity
2009-03-23 17:32     ` Christoph Hellwig
2009-03-23 19:58     ` Avi Kivity
2009-03-23 20:32       ` Anthony Liguori
2009-03-23 17:26   ` Christoph Hellwig

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=20090323184827.GA14826@lst.de \
    --to=hch@lst.de \
    --cc=avi@redhat.com \
    --cc=hch@infradead.org \
    --cc=kvm@vger.kernel.org \
    --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).