From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.3 development update, 18 March
Date: Wed, 20 Mar 2013 02:33:08 +0100 [thread overview]
Message-ID: <1363743188.3042.56.camel@Solace> (raw)
In-Reply-To: <CAFLBxZarvoLrg8kPvzc30vQ4vJOF8D6wK2Fok5xiaSy=KHMHNA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1749 bytes --]
On lun, 2013-03-18 at 12:13 +0000, George Dunlap wrote:
> This information will be mirrored on the Xen 4.3 Roadmap wiki page:
> http://wiki.xen.org/wiki/Xen_Roadmap/4.3
>
> [...]
>
> == Not yet complete ==
>
> * NUMA scheduler affinity
> critical
> owner: dario@citrix
> status: Patches posted
> prognosis: Excellent
>
This is mostly done. Last round received all the needed Ack-s, with only
some minor comments. I'll respin the series incorporating them ASAP, so
that it can finally get in.
We agreed on trying doing a small performance optimization before the
release... I'll see if I can get away with it quickly enough, after the
original series is checked in.
> * NUMA Memory migration
> owner: dario@citrix
> status: in progress
> prognosis: Fair
>
I'm not so sure about this anymore, I'm afraid. I'd have hoped to be in
a better spot wrt to this feature at this point but, unfortunately, I'm
still having issues with it.
I worked hard on it and am continuing doing so, and I will probably get
to release something during the rest of this week, or during the next
one. However, I'm not sure it would be wise to throw it in at this
stage... Perhaps we can make it a tech. preview?
Don't get me wrong, I'm happy to keep trying, just giving an heads up
(which I probably should have done before, but, apparently, I'm still
really bad at predicting how long it will take me to find and fix
bugs! :-P)
Regards,
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: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-03-20 1:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 12:13 Xen 4.3 development update, 18 March George Dunlap
2013-03-18 12:27 ` Ian Campbell
2013-03-18 12:31 ` Stefano Stabellini
2013-03-18 13:47 ` Ian Campbell
2013-03-19 15:36 ` George Dunlap
2013-03-21 19:32 ` Stefano Stabellini
2013-03-18 13:11 ` Jan Beulich
2013-03-18 13:39 ` Konrad Rzeszutek Wilk
2013-03-19 15:41 ` George Dunlap
2013-03-19 13:24 ` Daniel Kiper
2013-03-19 15:48 ` George Dunlap
2013-03-19 15:53 ` George Dunlap
2013-03-20 10:57 ` James Harper
2013-03-19 16:00 ` Wei Liu
2013-03-20 1:33 ` Dario Faggioli [this message]
2013-03-21 9:19 ` Roger Pau Monné
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=1363743188.3042.56.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@eu.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).