From: Dario Faggioli <dario.faggioli@citrix.com>
To: "Lars Kurth" <lars.kurth@citrix.com>,
"Juergen Groß" <jgross@suse.com>,
"George Dunlap" <George.Dunlap@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"committers@xenproject.org" <committers@xenproject.org>
Subject: Re: [For 4.9] Updating https://wiki.xenproject.org/wiki/Xen_Project_Release_Features to reflect support status of new features
Date: Tue, 27 Jun 2017 17:44:44 +0200 [thread overview]
Message-ID: <1498578284.7288.2.camel@citrix.com> (raw)
In-Reply-To: <D577F949.38A61%lars.kurth@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1038 bytes --]
On Tue, 2017-06-27 at 13:04 +0200, Lars Kurth wrote:
> > On 06/27/2017 12:33 PM, George Dunlap wrote:
> > > > == On A / B: I think we should add ==
> > > > - Resource Management > Null Scheduler : tech preview or
> > > > experimental
> > >
> > > I think that the interface is probably in a final form, the code
> > > is
> > > complete, and there are no known bugs or issues; so I'd say tech
> > > preview.
> > >
I agree. There's potential for new features and improvement, like
supporting soft-affinity (not for scheduling, as all is static, but for
NUMA placement reasons) and/or introducing tracing in there.
But all are the kind of improvement that happens even for supported
features.
> > > Dario, any opinions?
>
I think Tech Preview is ok.
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-27 15:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 8:53 [For 4.9] Updating https://wiki.xenproject.org/wiki/Xen_Project_Release_Features to reflect support status of new features Lars Kurth
2017-06-27 9:48 ` Razvan Cojocaru
2017-06-27 10:41 ` Lars Kurth
2017-06-27 17:47 ` Tamas K Lengyel
2017-06-27 10:33 ` George Dunlap
2017-06-27 10:54 ` Lars Kurth
2017-06-27 10:57 ` Juergen Groß
2017-06-27 11:04 ` Lars Kurth
2017-06-27 15:23 ` Wei Liu
2017-06-27 15:44 ` Dario Faggioli [this message]
2017-06-27 11:02 ` George Dunlap
2017-06-27 11:06 ` Lars Kurth
2017-06-27 13:25 ` Oleksandr Andrushchenko
2017-06-27 13:28 ` Oleksandr Andrushchenko
2017-06-27 13:30 ` Lars Kurth
2017-06-27 13:32 ` Oleksandr Andrushchenko
2017-06-27 16:00 ` Julien Grall
2017-06-27 16:16 ` Jan Beulich
2017-06-27 21:02 ` Lars Kurth
2017-08-17 14:48 ` Julien Grall
2017-08-17 14:51 ` Lars Kurth
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=1498578284.7288.2.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=committers@xenproject.org \
--cc=jgross@suse.com \
--cc=lars.kurth@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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.