From: David Vrabel <david.vrabel@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: Thu, 23 Jun 2016 17:28:35 +0100 [thread overview]
Message-ID: <576C0E33.2000308@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1606061030240.6721@sstabellini-ThinkPad-X260>
On 06/06/16 10:33, Stefano Stabellini wrote:
> # Goals
>
> The goal of the protocol is to provide networking capabilities to any
> guests, with the following added benefits:
>
> * 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.
I think it looks a bit odd to isolate the workload into a VM and then
blow a hole in the isolation by providing a "fat" RPC interface directly
to the privileged dom0 kernel.
I think you could probably present a regular VIF to the guest and use
SDN (e.g., openvswitch) to get your docker-like semantics.
David
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-23 16:28 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
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 [this message]
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=576C0E33.2000308@citrix.com \
--to=david.vrabel@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 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).