On 11 Nov 2013, at 12:43, Stefan Hajnoczi wrote: > Why is it necessary to push this task down into the host? I don't > understand the advantage of this approach except that maybe it works > around certain misconfigurations, I/O scheduler quirks, or plain old > bugs - all of which should be investigated and fixed at the source > instead of adding another layer of code to mask them.
I can see an argument why a guest with two very differently performing disks attached might be best served by two worker threads, particularly if one such thread was in part CPU bound (inventing this use case is left as an exercise for the reader). -- Alex Bligh
