Re: [Qemu-devel] [PATCH v3 2/5] [RFC] libqblock, user example

[Paolo Bonzini]

Il 30/08/2012 03:59, Wenchao Xia ha scritto:
>>>
>>
>> Busy waiting is not acceptable, and this is the reason why I had
>> suggested to keep AIO out of the design for now.
>>
>> You need to provide an implementation of AIO for either glib or
>> something else, but this is best done within QEMU first (and only later
>> moved to libqblock).
>>
>   It is similar to qemu's "select" type of AIO, while (true ==
> qb_aio_check(broker) is not neccessary but an example here
> to ensure write i/o is executed first.
>   Do you mean qemu's aio should be improved to another type of
> AIO API instead of select type? which kind of AIO api is preferred?

Using GSource to integrate with the QEMU main loop would be an idea.
qemu_aio_wait would remain.

However, this is not relevant to libqblock.  My point is that APIs are
hard to get right, and even harder if you try to do too many things in
the first iteration.

Paolo