On Wed, 20 May 2009 02:21:08 am Cam Macdonell wrote: > Avi Kivity wrote: > > Christian Bornträger wrote: > >>> To summarize, Anthony thinks it should use virtio, while I believe > >>> virtio is useful for exporting guest memory, not for importing host > >>> memory. Yes, precisely. But what's it *for*, this shared memory? Implementing shared memory is trivial. Using it is harder. For example, inter-guest networking: you'd have to copy packets in and out, making it slow as well as losing abstraction. The only interesting idea I can think of is exposing it to userspace, and having that run some protocol across it for fast app <-> app comms. But if that's your plan, you still have a lot of code the write! So I guess I'm missing the big picture here? Thanks, Rusty. -- 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
