[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130210.201035.2234938856222663233.davem@davemloft.net>
Date: Sun, 10 Feb 2013 20:10:35 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: acking@...are.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org,
gregkh@...uxfoundation.org, pv-drivers@...are.com,
kraxel@...hat.com
Subject: Re: [PATCH 0/1] VM Sockets for Linux upstreaming
From: Andy King <acking@...are.com>
Date: Wed, 6 Feb 2013 16:23:55 -0800
> 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[1] 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.
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists