qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Ryan Harper <ryanh@us.ibm.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH][RFC] Refactor AIO to allow multiple AIO implementations
Date: Thu, 11 Sep 2008 09:04:16 -0500	[thread overview]
Message-ID: <48C92560.4000501@us.ibm.com> (raw)
In-Reply-To: <48C91A00.3060403@redhat.com>

Gerd Hoffmann wrote:
> Anthony Liguori wrote:
>   
>> Gerd Hoffmann wrote:
>>     
>>> Hmm, what is the long-term plan for this?
>>>       
>> Step one is to move the generic aio bits out of block-raw-posix (which
>> this patch does).
>>
>> Step two is to move the posix-aio routines out of block-raw-posix.
>>
>> Step three would be to add a generic interface to allow block-raw-posix
>> to use multiple aio implementations
>>
>> Step four would be to add a new aio implementation
>>     
>
> Sounds good.
>
>   
>> (I think the best
>> route is a thread-pool based implementation).
>>     
>
> Not sure about that.  linux-aio would have the advantage that the kernel
> knows about all the requests in flight and probably can do a better job
> on I/O ordering and scheduling then.  But once we can have multiple
> different implementations we can just try ;)
>   

But linux-aio doesn't work unless you're using O_DIRECT so for a lot of 
users, it's not very helpful.

Regards,

Anthony Liguori

> cheers,
>   Gerd
>
>   

      parent reply	other threads:[~2008-09-11 14:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10 15:49 [Qemu-devel] [PATCH][RFC] Refactor AIO to allow multiple AIO implementations Anthony Liguori
2008-09-11  7:48 ` [Qemu-devel] " Gerd Hoffmann
2008-09-11 12:45   ` Anthony Liguori
2008-09-11 13:15     ` Gerd Hoffmann
2008-09-11 13:28       ` Jamie Lokier
2008-09-11 14:09         ` Anthony Liguori
2008-09-11 14:04       ` Anthony Liguori [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=48C92560.4000501@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=ryanh@us.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 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).