From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH for-4.7] docs: Feature Levelling feature document
Date: Wed, 1 Jun 2016 13:05:18 +0100 [thread overview]
Message-ID: <574ECF7E.8080004@citrix.com> (raw)
In-Reply-To: <22350.47106.304924.235480@mariner.uk.xensource.com>
On 01/06/16 11:25, Ian Jackson wrote:
> Andrew Cooper writes ("[PATCH for-4.7] docs: Feature Levelling feature document"):
>> +N.B. `xl`, being inherently a single-host toolstack, doesn't make use of these
>> +levelling improvements. These features are of interest to higher level
>> +toolstacks such as `libvirt` or `XAPI`.
> I don't think this is quite the right spin, IYSWIM. xl does not
> currently provide any way to sort this stuff out. But in principle, I
> think there would be ways that it could.
>
> I would prefer a wording which was more encouraging to future
> improvements. Shall I suggest something ?
I guess there are two different issues here. (Note: I am specifically
distinguishing `xl` as a toolstack itself, from libxl which is a just a
library.)
Simply exposing the levelling/featureset information in `xl info` is
certainly a possible thing to do. Joao has some plans for surfacing the
levelling information in libxl for libvirt to use.
However, without a fundamental redesign of how xl works, it isn't going
to gain multi-host knowledge and consideration during domain creation.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-01 12:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 17:05 [PATCH for-4.7] docs: Feature Levelling feature document Andrew Cooper
2016-06-01 9:29 ` Jan Beulich
2016-06-03 15:36 ` Andrew Cooper
2016-06-03 15:42 ` Jan Beulich
2016-06-03 15:53 ` Andrew Cooper
2016-06-01 9:41 ` Wei Liu
2016-06-01 10:25 ` Ian Jackson
2016-06-01 12:05 ` Andrew Cooper [this message]
2016-06-01 12:14 ` Ian Jackson
2016-06-01 13:11 ` Andrew Cooper
2016-06-03 14:59 ` [PATCH v2 " Ian Jackson
2016-06-03 15:35 ` 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=574ECF7E.8080004@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=wei.liu2@citrix.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 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).