From: Dario Faggioli <dario.faggioli@citrix.com>
To: butian huang <11221079@zju.edu.cn>
Cc: "juergen.gross" <juergen.gross@ts.fujitsu.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
JBeulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 00 of 10 [RFC]] Automatically place guestonhost's NUMA nodes with xl
Date: Thu, 7 Mar 2013 02:39:19 +0100 [thread overview]
Message-ID: <1362620359.30266.14.camel@Abyss> (raw)
In-Reply-To: <5137EE09.036835.02212@zju.edu.cn>
[-- Attachment #1.1: Type: text/plain, Size: 945 bytes --]
On gio, 2013-03-07 at 01:31 +0000, butian huang wrote:
> hello，Dario
>
Hi,
> Thanks for your help!
>
You're welcome. :-)
> I get the xen code from "git://xenbits.xen.org/xen.git",but I can not find your code about three NUMA placement policies,why??
>
Because for the final version that was included in the code you're
looking at, we killed that "three policies" part. What you have there is
only one placement algorithm, enabled and active by default, which tries
to figure out the smallest possible number of nodes where to create a
new guest.
If you have the sources handy, check out this file:
docs/misc/xl-numa-placement.markdown
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
prev parent reply other threads:[~2013-03-07 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 1:31 [PATCH 00 of 10 [RFC]] Automatically place guestonhost's NUMA nodes with xl butian huang
2013-03-07 1:39 ` Dario Faggioli [this message]
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=1362620359.30266.14.camel@Abyss \
--to=dario.faggioli@citrix.com \
--cc=11221079@zju.edu.cn \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=juergen.gross@ts.fujitsu.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.