From: Andre Przywara <andre.przywara@amd.com>
To: Dario Faggioli <raistlin@linux.it>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
Juergen Gross <juergen.gross@ts.fujitsu.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel <xen-devel@lists.xen.org>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH 2 of 4 v7/leftover] libxl: enable automatic placement of guests on NUMA nodes
Date: Thu, 26 Jul 2012 14:03:43 +0200 [thread overview]
Message-ID: <5011321F.6080601@amd.com> (raw)
In-Reply-To: <6dab5496964de0830f1a.1343140929@Solace>
On 07/24/2012 04:42 PM, Dario Faggioli wrote:
> If a domain does not have a VCPU affinity, try to pin it automatically
> to some PCPUs. This is done taking into account the NUMA characteristics
> of the host. In fact, we look for a combination of host's NUMA nodes
> with enough free memory and number of PCPUs for the new domain, and pin
> it to the VCPUs of those nodes.
I have tested this version 7 on my box in various configurations:
1. Homogeneous memory distribution: 8 nodes, each 16 GB
2. "Odd" configuration: 8 nodes, 4 have 8 GB, 4 have 16 GB
3 Flat memory (by using cpus="all")
I created up to 32 guests with 2 VCPUs and 2 GB each and observed the
distribution after every 8th guest.
Another round with 2 VCPU guests, but this time with memory sizes
varying from 512MB to 5120MB.
The placement was running well in all cases.
The only thing I saw as a little sub-optimal placement in the odd
configuration (2) with the differently sized guests. This is probably a
side effect of Dom0 ballooning, which is not really NUMA aware AFAIK.
This leads to a situation, where some nodes just by chance have less
memory than a certain guest needs and so are not considered candidates.
I think we can perfectly tolerate this behavior for now. I didn't see
anything strange with config 1.
So this patch gets my:
Tested-by: Andre Przywara <andre.przywara@amd.com>
Please apply to 4.2-unstable!
Regards,
Andre.
next prev parent reply other threads:[~2012-07-26 12:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 14:42 [PATCH 0 of 4 v7/leftover] Automatic NUMA placement for xl Dario Faggioli
2012-07-24 14:42 ` [PATCH 1 of 4 v7/leftover] libxl: kill the need for checking and linking to libm Dario Faggioli
2012-07-25 16:40 ` Ian Campbell
2012-07-24 14:42 ` [PATCH 2 of 4 v7/leftover] libxl: enable automatic placement of guests on NUMA nodes Dario Faggioli
2012-07-26 12:03 ` Andre Przywara [this message]
2012-07-26 13:54 ` Dario Faggioli
2012-07-26 14:14 ` Ian Jackson
2012-07-26 16:00 ` Dario Faggioli
2012-07-24 14:42 ` [PATCH 3 of 4 v7/leftover] libxl: have NUMA placement deal with cpupools Dario Faggioli
2012-07-26 14:20 ` Ian Jackson
2012-07-24 14:42 ` [PATCH 4 of 4 v7/leftover] Some automatic NUMA placement documentation Dario Faggioli
2012-07-26 14:22 ` Ian Jackson
2012-07-26 14:31 ` Ian Campbell
2012-07-26 14:42 ` [PATCH 0 of 4 v7/leftover] Automatic NUMA placement for xl Ian Campbell
2012-07-26 15:47 ` Dario Faggioli
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=5011321F.6080601@amd.com \
--to=andre.przywara@amd.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=juergen.gross@ts.fujitsu.com \
--cc=raistlin@linux.it \
--cc=roger.pau@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.