Richard W.M. Jones wrote: > On Mon, Jul 27, 2009 at 06:44:28PM -0500, Anthony Liguori wrote: > >> It really suggests that you need _one_ vmchannel that's exposed to >> userspace with a single userspace daemon that consumes it. >> > > ... or a more flexible API. I don't like having fixed /dev/vmch* > devices either. > Indeed. > A long time ago (on a mailing list not so far away) there was a much > better userspace API proposed, which had a separate AF_VMCHANNEL > address family. > > That API works much more like TCP sockets, except without requiring > network devices: > Dave Miller nacked that approach with a sledgehammer instead preferring that we just use standard TCP/IP which is what led to the current implementation using slirp. A userspace daemon with unix domain sockets could give a similar solution. Regards, Anthony Liguori _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
