Hi Anthony,
> There's an aio_init in block-raw-posix.c that sets the thread count to
> 1. If you #if 0 out that block, or increase the threads to something
> higher (like 16), you should see multiple simultaneous requests. Sorry
> about that, I had that in a different patch in my tree.
Thank
Ryo Tsuruta wrote:
> Hi Anthony.
>
>
>> The attached patch implements AIO support for the virtio backend so if this
>> is the case, you should see the proper proportions.
>>
>
> First, thank you very much for making the patch.
> I ran the same test program on KVM with the patch but I wasn
Hi Anthony.
> The attached patch implements AIO support for the virtio backend so if this
> is the case, you should see the proper proportions.
First, thank you very much for making the patch.
I ran the same test program on KVM with the patch but I wasn't able to
get good results.
I checked the
Ryo Tsuruta wrote:
Hi,
If you are using virtio drivers in the guest (which I presume you are
given the reference to /dev/vda), try using the following -drive syntax:
-drive file=/dev/mapper/ioband1,if=virtio,boot=on,cache=off
This will force the use of O_DIRECT. By default, QEMU does not
Hi,
> If you are using virtio drivers in the guest (which I presume you are
> given the reference to /dev/vda), try using the following -drive syntax:
>
> -drive file=/dev/mapper/ioband1,if=virtio,boot=on,cache=off
>
> This will force the use of O_DIRECT. By default, QEMU does not open
> with
Hi,
> If you are using virtio drivers in the guest (which I presume you are given
> the reference to /dev/vda), try using the following -drive syntax:
>
> -drive file=/dev/mapper/ioband1,if=virtio,boot=on,cache=off
>
> This will force the use of O_DIRECT. By default, QEMU does not open with
> O
Avi Kivity wrote:
> Anthony Liguori wrote:
>>
>> If you are using virtio drivers in the guest (which I presume you are
>> given the reference to /dev/vda), try using the following -drive syntax:
>>
>> -drive file=/dev/mapper/ioband1,if=virtio,boot=on,cache=off
>>
>> This will force the use of O_DI
Anthony Liguori wrote:
> Hi Ryo,
>
> Ryo Tsuruta wrote:
>
>> Hello all,
>>
>> I've implemented a block device which throttles block I/O bandwidth,
>> which I called dm-ioband, and been trying to throttle I/O bandwidth on
>> KVM environment. But unfortunately it doesn't work well, the number of
Hi Ryo,
Ryo Tsuruta wrote:
> Hello all,
>
> I've implemented a block device which throttles block I/O bandwidth,
> which I called dm-ioband, and been trying to throttle I/O bandwidth on
> KVM environment. But unfortunately it doesn't work well, the number of
> issued I/Os is not according to the
Hello all,
I've implemented a block device which throttles block I/O bandwidth,
which I called dm-ioband, and been trying to throttle I/O bandwidth on
KVM environment. But unfortunately it doesn't work well, the number of
issued I/Os is not according to the bandwidth setting.
On the other hand, I
10 matches
Mail list logo
