From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Elena Ufimtseva <ufimtseva@gmail.com>, dario.faggioli@citrix.com
Cc: Wei Liu <wei.liu2@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: vnuma toolstack extension request
Date: Wed, 24 Sep 2014 11:15:11 -0400 [thread overview]
Message-ID: <20140924151511.GA6771@laptop.dumpdata.com> (raw)
In-Reply-To: <CAEr7rXi5sQj59LB=J2_4SRe0MRdTPwZjF9_CeSdym5kXX2vr9Q@mail.gmail.com>
On Wed, Sep 24, 2014 at 12:30:58AM -0400, Elena Ufimtseva wrote:
> Hello toolstack maintainers
>
> I would like to request extension for vNUMA toolstack.
> The patches are on the way (latest tomorrow) and it will need to go through
> review process as well.
Hey Elena,
Before you invest time in this, a couple of questions:
- Dariof was interested in merging this with his auto NUMA placement code.
That piece of code does not look simple and I think he volunteered
to do it. However he has also been busy reviewing Xen RT patches so
I figured he hasn't yet done that.
- Since it would interact with auto NUMA placement and expose new
logic in libxl we run in the problem of the 'stable' API that we
MUST preserve. That is a worry - and will require scrutinity.
- I think (and please correct me if I am wrong) that it would require
at least two revisions to be posted.
- What is the impact if the toolstack patches go in Xen 4.6?
Thank you.
>
>
> --
> Elena
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-09-24 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 4:30 vnuma toolstack extension request Elena Ufimtseva
2014-09-24 15:15 ` Konrad Rzeszutek Wilk [this message]
2014-09-24 15:24 ` Elena Ufimtseva
2014-09-24 16:09 ` Dario Faggioli
2014-09-24 16:59 ` Konrad Rzeszutek Wilk
2014-09-24 17:08 ` Elena Ufimtseva
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=20140924151511.GA6771@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dario.faggioli@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=ufimtseva@gmail.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 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.