On 11/14/2010 01:05 PM, Avi Kivity wrote:
I agree, but let's enable virtio-ioeventfd carefully because bad code
is out there.
Sure. Note as long as the thread waiting on ioeventfd doesn't consume
too much cpu, it will awaken quickly and we won't have the
"transaction per timeslice" effect.
btw, what about virtio-blk with linux-aio? Have you benchmarked that
with and without ioeventfd?
And, what about efficiency? As in bits/cycle?
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
