On Tue, Jul 17, 2012 at 01:03:39PM +0100, Stefan Hajnoczi wrote:

On Tue, Jul 17, 2012 at 12:54 PM, Michael S. Tsirkin [off-list ref] wrote:

quoted

quoted

Knowing the answer to that is important before anyone can say whether
this approach is good or not.

Stefan

Why is it?

Because there might be a fix to kvmtool which closes the gap.  It
would be embarassing if vhost-blk was pushed just because no one
looked into what is actually going on.

Embarrasing to whom? Is someone working on an optimization that
makes the work in question redundant, with posting just around
the corner? Then maybe the thing to do is just wait a bit.

Or are there no specific plans even, just a vague "sometime
in the future someone might take Asias' patches and profile them see if
anything maybe sticks out"? Then maybe not making everyone
wait years for this will serve users better.

And on the flipside, hard evidence of an overhead that cannot be
resolved could be good reason to do more vhost devices in the future.

How can one have hard evidence of an overhead that cannot be resolved?
Any problem can be resolved in an infinite number of ways.

Either way, it's useful to do this before going further.

Stefan

I think each work should be discussed on its own merits.  Maybe
vhost-blk is just well written. So? What is your conclusion?

-- 
MST