On Tue, Mar 05, 2013 at 09:46:30PM +0100, Benoît Canet wrote:
> > You need to set a more specific goal. Some questions to get started:
> > * Which workloads do you care about and what are their
> > characteristics (sequential or random I/O, queue depth)?
> > * Do you care about 1 vcpu guests or
On 03/05/2013 11:59 PM, Stefan Hajnoczi wrote:
>> I am looking for a way to help improving qemu block performance.
>> >
>> > APIC-V is a work in progress and the two options with public code are
>> > vhost-*
>> > and virtio-blk-dataplane.
>> >
>> > The way of doing seems very similar (bypassing th
> You need to set a more specific goal. Some questions to get started:
> * Which workloads do you care about and what are their
> characteristics (sequential or random I/O, queue depth)?
> * Do you care about 1 vcpu guests or 4+ vcpu guests? (SMP scalability)
> * Are you using an image format?
On Tue, Mar 5, 2013 at 3:18 PM, Benoît Canet wrote:
> I am looking for a way to help improving qemu block performance.
>
> APIC-V is a work in progress and the two options with public code are vhost-*
> and virtio-blk-dataplane.
>
> The way of doing seems very similar (bypassing the qemu lock) and
Hello,
I am looking for a way to help improving qemu block performance.
APIC-V is a work in progress and the two options with public code are vhost-*
and virtio-blk-dataplane.
The way of doing seems very similar (bypassing the qemu lock) and dedicating
a thread to each emulated virtio block dev
