From: Cornelia Huck <cohuck@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-dev@lists.oasis-open.org,
Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Ian Campbell <ian.campbell@docker.com>
Subject: Re: [virtio-dev] [PATCH v10] vsock: add vsock device
Date: Fri, 30 Nov 2018 10:00:52 +0100 [thread overview]
Message-ID: <20181130100052.0a22ea72.cohuck@redhat.com> (raw)
In-Reply-To: <20181129181659.21284-1-stefanha@redhat.com>
On Thu, 29 Nov 2018 18:16:59 +0000
Stefan Hajnoczi <stefanha@redhat.com> wrote:
> The virtio vsock device is a zero-configuration socket communications
> device. It is designed as a guest<->host management channel suitable
> for communicating with guest agents.
>
> vsock is designed with the sockets API in mind and the driver is
> typically implemented as an address family (at the same level as
> AF_INET). Applications written for the sockets API can be ported with
> minimal changes (similar amount of effort as adding IPv6 support to an
> IPv4 application).
>
> Unlike the existing console device, which is also used for guest<->host
> communication, multiple clients can connect to a server at the same time
> over vsock. This limitation requires console-based users to arbitrate
> access through a single client. In vsock they can connect directly and
> do not have to synchronize with each other.
>
> Unlike network devices, no configuration is necessary because the device
> comes with its address in the configuration space.
>
> The vsock device was prototyped by Gerd Hoffmann and Asias He. I picked
> the code and design up from them.
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/27
> Cc: Michael S. Tsirkin <mst@redhat.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
I have not reviewed it in detail; but in general, the spec looks good
to me.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2018-11-30 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 18:16 [virtio-dev] [PATCH v10] vsock: add vsock device Stefan Hajnoczi
2018-11-30 9:00 ` Cornelia Huck [this message]
2018-11-30 21:23 ` [virtio-dev] " Michael S. Tsirkin
2018-12-13 9:16 ` Stefan Hajnoczi
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=20181130100052.0a22ea72.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=ian.campbell@docker.com \
--cc=imbrenda@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.