From: "Jan Beulich" <JBeulich@suse.com>
To: Dongxiao Xu <dongxiao.xu@intel.com>
Cc: "Andrew Cooper(andrew.cooper3@citrix.com)"
<andrew.cooper3@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen Platform QoS design discussion
Date: Tue, 06 May 2014 08:55:28 +0100 [thread overview]
Message-ID: <5368B190020000780000F2FA@mail.emea.novell.com> (raw)
In-Reply-To: <40776A41FC278F40B59438AD47D147A9119FE6BB@SHSMSX104.ccr.corp.intel.com>
>>> On 06.05.14 at 03:40, <dongxiao.xu@intel.com> wrote:
> Since there is no further comments, I suppose we all agreed on making the
> hypercall per-domain and use data copying mechanism between hypervisor and
> Dom0 tool stack?
I think Andrew wasn't really in agreement with this, and I also think
the ball is in your court to tell us whether indeed the prevalent usage
model would benefit from that choice of yours. Considering just
OpenStack, as I said before, seems a little narrow minded to me.
That said, I'm neverthtless not really opposed to the per-domain-
copying model.
Jan
next prev parent reply other threads:[~2014-05-06 7:55 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 16:47 Xen Platform QoS design discussion Xu, Dongxiao
2014-04-30 17:02 ` Ian Campbell
2014-05-01 0:56 ` Xu, Dongxiao
2014-05-02 9:23 ` Jan Beulich
2014-05-02 12:30 ` Xu, Dongxiao
2014-05-02 12:40 ` Jan Beulich
2014-05-04 0:46 ` Xu, Dongxiao
2014-05-06 9:10 ` Ian Campbell
2014-05-06 1:40 ` Xu, Dongxiao
2014-05-06 7:55 ` Jan Beulich [this message]
2014-05-06 10:06 ` Andrew Cooper
2014-05-07 2:08 ` Xu, Dongxiao
2014-05-07 9:10 ` Ian Campbell
2014-05-07 13:26 ` George Dunlap
2014-05-07 21:18 ` Andrew Cooper
2014-05-08 5:21 ` Xu, Dongxiao
2014-05-08 11:25 ` Andrew Cooper
2014-05-09 2:41 ` Xu, Dongxiao
2014-05-13 1:53 ` Xu, Dongxiao
2014-05-16 5:11 ` Xu, Dongxiao
2014-05-19 11:28 ` George Dunlap
2014-05-19 11:45 ` Jan Beulich
2014-05-19 12:13 ` George Dunlap
2014-05-19 12:41 ` Jan Beulich
2014-05-22 8:19 ` Xu, Dongxiao
2014-05-22 8:39 ` Jan Beulich
2014-05-22 9:27 ` George Dunlap
2014-05-26 0:51 ` Xu, Dongxiao
2014-05-29 0:45 ` Xu, Dongxiao
2014-05-29 7:01 ` Jan Beulich
2014-05-29 7:31 ` Xu, Dongxiao
2014-05-29 9:11 ` Jan Beulich
2014-05-30 9:10 ` Ian Campbell
2014-05-30 11:17 ` Jan Beulich
2014-05-30 12:33 ` Ian Campbell
2014-06-05 0:48 ` Xu, Dongxiao
2014-06-05 10:43 ` George Dunlap
2014-05-29 9:13 ` Andrew Cooper
2014-05-30 1:07 ` Xu, Dongxiao
2014-05-30 6:23 ` Jan Beulich
2014-05-30 7:51 ` Xu, Dongxiao
2014-05-30 11:15 ` Jan Beulich
2014-05-02 12:50 ` Andrew Cooper
2014-05-04 2:34 ` Xu, Dongxiao
2014-05-06 9:12 ` Ian Campbell
2014-05-06 10:00 ` Andrew Cooper
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=5368B190020000780000F2FA@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=Ian.Campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=dongxiao.xu@intel.com \
--cc=xen-devel@lists.xen.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.