[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 7 Jul 2015 11:31:12 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Dexuan Cui <decui@...rosoft.com>
Cc: gregkh@...uxfoundation.org, davem@...emloft.net,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
driverdev-devel@...uxdriverproject.org, olaf@...fle.de,
apw@...onical.com, jasowang@...hat.com, kys@...rosoft.com,
haiyangz@...rosoft.com
Subject: Re: [PATCH 6/7] hvsock: introduce Hyper-V VM Sockets feature
On Mon, 6 Jul 2015 07:47:29 -0700
Dexuan Cui <decui@...rosoft.com> wrote:
> Hyper-V VM sockets (hvsock) supplies a byte-stream based communication
> mechanism between the host and a guest. It's kind of TCP over VMBus, but
> the transportation layer (VMBus) is much simpler than IP. With Hyper-V VM
> Sockets, applications between the host and a guest can talk with each
> other directly by the traditional BSD-style socket APIs.
>
> Hyper-V VM Sockets is only available on Windows 10 host and later. The
> patch implements the necessary support in the guest side by introducing
> a new socket address family AF_HYPERV.
>
> Signed-off-by: Dexuan Cui <decui@...rosoft.com>
Is there any chance that AF_VSOCK could be used with different transport
for VMware and Hyper-V. Better to make guest applications host independent.
--
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