On Wed, Aug 12, 2009 at 02:22:38PM -0500, Anthony Liguori wrote: > Michael S. Tsirkin wrote: >>> >>> We discussed this before, and I still think this could be directly derived >>> from struct virtqueue, in the same way that vring_virtqueue is derived from >>> struct virtqueue. >>> >> >> I prefer keeping it simple. Much of abstraction in virtio is due to the >> fact that it needs to work on top of different hardware emulations: >> lguest,kvm, possibly others in the future. vhost is always working on >> real hardware, using eventfd as the interface, so it does not need that. >> > > Actually, vhost may not always be limited to real hardware. Yes, any ethernet device will do. What I mean is that vhost does not deal with emulation at all. All setup is done in userspace. > > We may on day use vhost as the basis of a driver domain. There's quite > a lot of interest in this for networking. You can use veth for this. This works today. > At any rate, I'd like to see performance results before we consider > trying to reuse virtio code. > > Regards, > > Anthony Liguori -- 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
