Messages in this thread | | | From | "Jorgen S. Hansen" <> | Subject | Re: [PATCH] vsock: only load vmci transport on VMware hypervisor by default | Date | Wed, 6 Sep 2017 14:11:22 +0000 |
| |
> On Aug 31, 2017, at 1:54 PM, Stefan Hajnoczi <stefanha@redhat.com> wrote: > > On Tue, Aug 29, 2017 at 03:37:07PM +0000, Jorgen S. Hansen wrote: >>> On Aug 29, 2017, at 4:36 AM, Dexuan Cui <decui@microsoft.com> wrote: >> If we allow multiple host side transports, virtio host side support and >> vmci should be able to coexist regardless of the order of initialization. > > That sounds good to me. > > This means af_vsock.c needs to be aware of CID allocation. Currently the > vhost_vsock.ko driver handles this itself (it keeps a list of CIDs and > checks that they are not used twice). It should be possible to move > that state into af_vsock.c so we have <cid, host_transport> pairs. >
Yes, that was my thinking as well.
> I'm currently working on NFS over AF_VSOCK and sock_diag support (for > ss(8) and netstat-like tools). > > Multi-transport support is lower priority for me at the moment. I'm > happy to review patches though. If there is no progress on this by the > end of the year then I will have time to work on it. >
I’ll try to find time to write a more coherent proposal in the coming weeks, and we can discuss that.
> Are either of you are in Prague, Czech Republic on October 25-27 for > Linux Kernel Summit, Open Source Summit Europe, Embedded Linux > Conference Europe, KVM Forum, or MesosCon Europe?
No, I won’t be there.
Thanks, Jorgen
| |