Highlighted
Contributor
Contributor

Mainlined Linux VSOCK module: why vsock and not vmw_vsock?

Jump to solution

Hey,

I've been searching this for quite a while now, and am just curious, why did the VMCI module name end up as "vmw_vmci", but the VSOCK module became "vsock" (same name as the original Workstation bundled one).

Thanks for your time,

Poloisfej

1 Solution

Accepted Solutions
Highlighted
VMware Employee
VMware Employee

I forwarded your question on to our vsock/vmci experts, and they came back with the answer: vsock is a hypervisor-independent interface.  vmci is a VMware-specific interface which is used as a transport for vsock.

Hence vsock has no "vmw_" prefix, but vmw_vmci does.

I hope this is a satisfactory explanation.  It cleared things up for me.

Cheers

--

Darius

View solution in original post

2 Replies
Highlighted
VMware Employee
VMware Employee

I forwarded your question on to our vsock/vmci experts, and they came back with the answer: vsock is a hypervisor-independent interface.  vmci is a VMware-specific interface which is used as a transport for vsock.

Hence vsock has no "vmw_" prefix, but vmw_vmci does.

I hope this is a satisfactory explanation.  It cleared things up for me.

Cheers

--

Darius

View solution in original post

Highlighted
Contributor
Contributor

dariusd Fantastic, thank-you.

0 Kudos