On 08/01/2011 12:18 PM, Liu Yuan wrote:
Agree. vhost-net works around the lack of async zero copy networking
interface. Block I/O on the other hand does have such an interface,
and in addition transaction rates are usually lower. All we're
saving is the syscall overhead.
Personally I too agree with Sasha Levin. But vhost-blk is the first
fast prototype that is supposed to act as a code base to do further
optimisation, which I plan to utilize kernel's internal stuff like
BIO layer, that can not be accessed from user space, to maximize the
performance for raw disk based block IO.
Is there anything in the bio layer which is not exposed by linux-aio?
Or is linux-aio slow in translating from vfs ops to bio ops?
--
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
