From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Stefano Stabellini <stefano@aporeto.com>, xen-devel@lists.xenproject.org
Cc: joao.m.martins@oracle.com, wei.liu2@citrix.com, roger.pau@citrix.com
Subject: Re: RFC: XenSock brainstorming
Date: Mon, 6 Jun 2016 10:57:31 +0100 [thread overview]
Message-ID: <5755490B.8030000@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1606061030240.6721@sstabellini-ThinkPad-X260>
On 06/06/16 10:33, Stefano Stabellini wrote:
> Hi all,
>
> a couple of months ago I started working on a new PV protocol for
> virtualizing syscalls. I named it XenSock, as its main purpose is to
> allow the implementation of the POSIX socket API in a domain other than
> the one of the caller. It allows connect, accept, recvmsg, sendmsg, etc
> to be implemented directly in Dom0. In a way this is conceptually
> similar to virtio-9pfs, but for sockets rather than filesystem APIs.
> See this diagram as reference:
>
> https://docs.google.com/presentation/d/1z4AICTY2ejAjZ-Ul15GTL3i_wcmhKQJA7tcXwhI3dys/edit?usp=sharing
>
> The frontends and backends could live either in userspace or kernel
> space, with different trade-offs. My current prototype is based on Linux
> kernel drivers but it would be nice to have userspace drivers too.
> Discussing where the drivers could be implemented it's beyond the scope
> of this email.
Just to confirm, you are intending to create a cross-domain transport
for all AF_ socket types, or just some?
>
>
> # Goals
>
> The goal of the protocol is to provide networking capabilities to any
> guests, with the following added benefits:
Throughout, s/Dom0/the backend/
I expect running the backend in dom0 will be the overwhelmingly common
configuration, but you should avoid designing the protocol for just this
usecase.
>
> * guest networking should work out of the box with VPNs, wireless
> networks and any other complex network configurations in Dom0
>
> * guest services should listen on ports bound directly to Dom0 IP
> addresses, fitting naturally in a Docker based workflow, where guests
> are Docker containers
>
> * Dom0 should have full visibility on the guest behavior and should be
> able to perform inexpensive filtering and manipulation of guest calls
>
> * XenSock should provide excellent performance. Unoptimized early code
> reaches 22 Gbit/sec TCP single stream and scales to 60 Gbit/sec with 3
> streams.
What happens if domU tries to open an AF_INET socket, and the domain has
both sockfront and netfront ? What happens if a domain has multiple
sockfronts?
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-06 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.10.1606021429410.16603@sstabellini-ThinkPad-X260>
[not found] ` <CAAe9sUHsKXsvD5aK9PHeTYRwq8+0Q9yXK2sPY+Fk=5kErBri8A@mail.gmail.com>
2016-06-06 9:33 ` RFC: XenSock brainstorming Stefano Stabellini
2016-06-06 9:57 ` Andrew Cooper [this message]
2016-06-06 10:16 ` Paul Durrant
2016-06-06 10:48 ` Stefano Stabellini
2016-06-06 10:25 ` Stefano Stabellini
2016-06-23 16:03 ` Stefano Stabellini
2016-06-23 16:57 ` Stefano Stabellini
2016-06-23 16:28 ` David Vrabel
2016-06-23 16:49 ` Stefano Stabellini
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=5755490B.8030000@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=joao.m.martins@oracle.com \
--cc=roger.pau@citrix.com \
--cc=stefano@aporeto.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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.