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 would be to add a generic interface to allow block-raw-posix
to use multiple aio implementations
Step four would be to add a new aio implementation
Sounds good.
(I think the best
route is a thread-pool based implementation).
Not sure about that. linux-aio would have the advantage that the kernel
knows about all the requests in flight and probably can do a better job
on I/O ordering and scheduling then. But once we can have multiple
different implementations we can just try ;)
But linux-aio doesn't work unless you're using O_DIRECT so for a lot of
users, it's not very helpful.
Regards,
Anthony Liguori
cheers,
Gerd
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
