From: David Vrabel <david.vrabel@citrix.com>
To: Stefano Stabellini <stefano@aporeto.com>,
Juergen Gross <jgross@suse.com>
Cc: lars.kurth@citrix.com, wei.liu2@citrix.com,
david.vrabel@citrix.com, xen-devel@lists.xenproject.org,
boris.ostrovsky@oracle.com, joao.m.martins@oracle.com,
roger.pau@citrix.com
Subject: Re: [DRAFT 1] XenSock protocol design document
Date: Fri, 8 Jul 2016 16:57:15 +0100 [thread overview]
Message-ID: <577FCD5B.6050205@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1607081421060.26575@sstabellini-ThinkPad-X260>
On 08/07/16 15:16, Stefano Stabellini wrote:
>
> http://pubs.opengroup.org/onlinepubs/7908799/xns/connect.html
Are you really guaranteeing full POSIX semantics for all these calls?
And not say, POSIX-like except where Linux decides to differ because
POSIX is dumb?
How is the guest (which expects the semantics of its own OS) going to
know that connect(2) to an external IP is going to behave differently to
say connect(2) to localhost?
Given:
a) The difficulties in reconciling the differences in behaviour and
features between remoted system calls and local ones.
b) The difficulty in fully specifying (and thus fully implementing) the
PV interface.
c) My belief that most of the advantages of this proposal can be
achieved with smarts in the backend.
I'm not sure there is much merit in discussing the finer points of the
protocol until these bigger architectural issues have been addressed.
David
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-08 15:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 11:23 [DRAFT 1] XenSock protocol design document Stefano Stabellini
2016-07-08 12:14 ` Juergen Gross
2016-07-08 14:16 ` Stefano Stabellini
2016-07-08 14:27 ` Juergen Gross
2016-07-08 15:57 ` David Vrabel [this message]
2016-07-08 16:52 ` Stefano Stabellini
2016-07-08 17:10 ` David Vrabel
2016-07-08 17:36 ` Stefano Stabellini
2016-07-08 17:11 ` David Vrabel
2016-07-11 10:59 ` Stefano Stabellini
2016-07-11 12:47 ` Paul Durrant
2016-07-12 17:39 ` Stefano Stabellini
2016-07-11 14:51 ` Joao Martins
2016-07-13 11:06 ` 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=577FCD5B.6050205@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=joao.m.martins@oracle.com \
--cc=lars.kurth@citrix.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).