Re: [kvm-devel] [PATCH 3/3] Implement linux-aio backend

2008-04-18 Thread Marcelo Tosatti
On Thu, Apr 17, 2008 at 02:26:52PM -0500, Anthony Liguori wrote: This patch introduces a Linux-aio backend that is disabled by default. To use this backend effectively, the user should disable caching and select it with the appropriate -aio option. For instance: qemu-system-x86_64 -drive

Re: [kvm-devel] [PATCH 3/3] Implement linux-aio backend

2008-04-18 Thread Anthony Liguori
Marcelo Tosatti wrote: On Thu, Apr 17, 2008 at 02:26:52PM -0500, Anthony Liguori wrote: This patch introduces a Linux-aio backend that is disabled by default. To use this backend effectively, the user should disable caching and select it with the appropriate -aio option. For instance:

Re: [kvm-devel] [PATCH 3/3] Implement linux-aio backend

2008-04-18 Thread Marcelo Tosatti
On Fri, Apr 18, 2008 at 10:18:33AM -0500, Anthony Liguori wrote: Sleeping in the context of vcpu's is extremely bad (eg virtio-block blocks in write() throttling which kills performance). It should wait on IO completions instead (qemu-kvm.c creates a pthread waitqueue to resolve that issue).

[kvm-devel] [PATCH 3/3] Implement linux-aio backend

2008-04-17 Thread Anthony Liguori
This patch introduces a Linux-aio backend that is disabled by default. To use this backend effectively, the user should disable caching and select it with the appropriate -aio option. For instance: qemu-system-x86_64 -drive foo.img,cache=off -aio linux There's no universal way to asynchronous