|author||David S. Miller <email@example.com>||2013-02-10 20:10:10 -0500|
|committer||David S. Miller <firstname.lastname@example.org>||2013-02-10 20:10:10 -0500|
|parent||Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (diff)|
|parent||VSOCK: Introduce VM Sockets (diff)|
Merge branch 'vsock'
Andy King says: ==================== In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the VM Sockets (VSOCK, formerly VMCI Sockets) (vsock) kernel module for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vsock kernel module. Unlike previous submissions, where the new socket family was entirely reliant on VMware's VMCI PCI device (and thus VMware's hypervisor), VM Sockets is now completely separated out into two parts, each in its own module: o Core socket code, which is transport-neutral and invokes transport callbacks to communicate with the hypervisor. This is vsock.ko. o A VMCI transport, which communicates over VMCI with the VMware hypervisor. This is vmw_vsock_vmci_transport.ko, and it registers with the core module as a transport. This should provide a path to introducing additional transports, for example virtio, with the ultimate goal being to make this new socket family hypervisor-neutral.  If Gerd tries it and determines this to be false (still), I'll ship him a keg of beer. ==================== Signed-off-by: David S. Miller <email@example.com>
Diffstat (limited to 'net/8021q')
0 files changed, 0 insertions, 0 deletions