From: David Vrabel <david.vrabel@citrix.com>
To: Stefano Stabellini <stefano@aporeto.com>
Cc: Juergen Gross <jgross@suse.com>,
lars.kurth@citrix.com, wei.liu2@citrix.com,
xen-devel@lists.xenproject.org, joao.m.martins@oracle.com,
boris.ostrovsky@oracle.com, roger.pau@citrix.com
Subject: Re: [DRAFT 1] XenSock protocol design document
Date: Fri, 8 Jul 2016 18:10:51 +0100 [thread overview]
Message-ID: <577FDE9B.8020600@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1607081713350.26575@sstabellini-ThinkPad-X260>
On 08/07/16 17:52, Stefano Stabellini wrote:
>
>> c) My belief that most of the advantages of this proposal can be
>> achieved with smarts in the backend.
>
> By backend do you mean netfront/netback? If so, I have already pointed
> out why that is not the case in previous emails as well as in this
> design document.
>
> If you remain unconvinced of the usefulness of this work, that's OK, we
> can agree to disagree. Many people work on things I don't believe
> particularly useful myself. I am not asking you to spend any time on
> this if you don't believe it serves a purpose. But please let the rest
> of the community work constructively together.
If you're only going to implement userspace frontends and backends, then
sure I can step out of this discussion. However, your initial prototype
drivers suggest you're aiming at in-kernel drivers.
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 17:11 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
2016-07-08 16:52 ` Stefano Stabellini
2016-07-08 17:10 ` David Vrabel [this message]
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=577FDE9B.8020600@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).