On 01/03/11 - 04:43:06PM, Eric Blake wrote:
On 05/17/2010 03:31 PM, Eric Blake wrote:
[adding Matthias on cc]
Reviving an old thread, as it is something I plan on working in the near
future.
On 05/17/2010 03:07 PM, Chris Lalancette wrote:
On 05/12/2010 11:26 PM, Eric Blake wrote:
On Tue, Jan 04, 2011 at 08:12:21AM -0500, Chris Lalancette wrote:
On 01/03/11 - 04:43:06PM, Eric Blake wrote:
On 05/17/2010 03:31 PM, Eric Blake wrote:
[adding Matthias on cc]
Reviving an old thread, as it is something I plan on working in the near
future.
On 05/17/2010
On 01/04/2011 09:33 AM, Daniel P. Berrange wrote:
Does this deserve a new iobackend element, or should it merely be a
new optional attribute of the existing driver element, as in:
driver name='qemu' type='qcow2' cache='none' iobackend='aiothreads'/
I slightly prefer making it a new attribute
On 05/17/2010 03:31 PM, Eric Blake wrote:
[adding Matthias on cc]
Reviving an old thread, as it is something I plan on working in the near
future.
On 05/17/2010 03:07 PM, Chris Lalancette wrote:
On 05/12/2010 11:26 PM, Eric Blake wrote:
From: Matthias Dahl mdv...@designassembly.de
qemu
On 05/12/2010 11:26 PM, Eric Blake wrote:
From: Matthias Dahl mdv...@designassembly.de
qemu allows the user to choose what io storage api should be used, either the
default (threads) or native (linux aio) which in the latter case can result in
better performance.
Thanks a lot to Eric
[adding Matthias on cc]
On 05/17/2010 03:07 PM, Chris Lalancette wrote:
On 05/12/2010 11:26 PM, Eric Blake wrote:
From: Matthias Dahl mdv...@designassembly.de
qemu allows the user to choose what io storage api should be used, either the
default (threads) or native (linux aio) which in the
From: Matthias Dahl mdv...@designassembly.de
qemu allows the user to choose what io storage api should be used, either the
default (threads) or native (linux aio) which in the latter case can result in
better performance.
Thanks a lot to Eric Blake and Matthias Bolte for their comments.
Red Hat
