On Tue, Aug 18, 2009 at 11:51:59AM -0400, Gregory Haskins wrote: > > It's not laughably trivial when you try to support the full feature set > > of kvm (for example, live migration will require dirty memory tracking, > > and exporting all state stored in the kernel to userspace). > > Doesn't vhost suffer from the same issue? If not, could I also apply > the same technique to support live-migration in vbus? vhost does this by switching to userspace for the duration of live migration. venet could do this I guess, but you'd need to write a userspace implementation. vhost just reuses existing userspace virtio. > With all due respect, I didnt ask you do to anything, especially not > abandon something you are happy with. > > All I did was push guest drivers to LKML. The code in question is > independent of KVM, and its proven to improve the experience of using > Linux as a platform. There are people interested in using them (by > virtue of the number of people that have signed up for the AlacrityVM > list, and have mailed me privately about this work). > > So where is the problem here? If virtio net in guest could be improved instead, everyone would benefit. I am doing this, and I wish more people would join. Instead, you change ABI in a incompatible way. So now, there's no single place to work on kvm networking performance. Now, it would all be understandable if the reason was e.g. better performance. But you say yourself it isn't. See the problem? -- MST -- 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
