From: Stephen Hemminger <stephen@networkplumber.org>
To: Dexuan Cui <decui@microsoft.com>
Cc: gregkh@linuxfoundation.org, davem@davemloft.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
driverdev-devel@linuxdriverproject.org, olaf@aepfle.de,
apw@canonical.com, jasowang@redhat.com, kys@microsoft.com,
haiyangz@microsoft.com
Subject: Re: [PATCH 6/7] hvsock: introduce Hyper-V VM Sockets feature
Date: Tue, 7 Jul 2015 11:31:12 -0700 [thread overview]
Message-ID: <20150707113112.408b6c5d@urahara> (raw)
In-Reply-To: <1436194049-27829-1-git-send-email-decui@microsoft.com>
On Mon, 6 Jul 2015 07:47:29 -0700
Dexuan Cui <decui@microsoft.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@microsoft.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.
next prev parent reply other threads:[~2015-07-07 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 14:47 [PATCH 6/7] hvsock: introduce Hyper-V VM Sockets feature Dexuan Cui
2015-07-07 9:37 ` Paul Bolle
2015-07-07 10:02 ` Dexuan Cui
2015-07-07 10:10 ` Olaf Hering
2015-07-07 10:20 ` Dexuan Cui
2015-07-07 10:58 ` Olaf Hering
2015-07-08 5:22 ` Dexuan Cui
2015-07-07 11:51 ` Paul Bolle
2015-07-07 18:31 ` Stephen Hemminger [this message]
2015-07-08 3:56 ` Dexuan Cui
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150707113112.408b6c5d@urahara \
--to=stephen@networkplumber.org \
--cc=apw@canonical.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).