Anthony Liguori wrote:
This patch refactors the AIO layer to allow multiple AIO implementations.
It's
only possible because of the recent signalfd() patch.
Right now, the AIO infrastructure is pretty specific to the block raw backend.
For other block devices to implement AIO, the
Gerd Hoffmann wrote:
Anthony Liguori wrote:
This patch refactors the AIO layer to allow multiple AIO implementations. It's
only possible because of the recent signalfd() patch.
Right now, the AIO infrastructure is pretty specific to the block raw backend.
For other block devices to
Gerd Hoffmann wrote:
Anthony Liguori wrote:
Gerd Hoffmann wrote:
Hmm, what is the long-term plan for this?
Step one is to move the generic aio bits out of block-raw-posix (which
this patch does).
Step two is to move the posix-aio routines out of block-raw-posix.
Step three
Jamie Lokier wrote:
I'm under the impression that linux-aio is better in every way, as
I think Anthony Liguori posted a while back:
Threads are a poor substitute for a proper AIO interface.
linux-aio gives you everything you could possibly want in an
interface since it allows you to
This patch refactors the AIO layer to allow multiple AIO implementations. It's
only possible because of the recent signalfd() patch.
Right now, the AIO infrastructure is pretty specific to the block raw backend.
For other block devices to implement AIO, the qemu_aio_wait function must
support
