From: Andre Przywara <andre.przywara@amd.com>
To: Juergen Gross <juergen.gross@ts.fujitsu.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: RFC: automatic NUMA placement
Date: Mon, 27 Sep 2010 23:46:59 +0200 [thread overview]
Message-ID: <4CA110D3.5050000@amd.com> (raw)
In-Reply-To: <4C921DDF.6020809@ts.fujitsu.com>
Juergen Gross wrote:
> Hi,
>
> I just stumbled upon the automatic pinning of vcpus on domain creation in
> case of NUMA.
> This behaviour is questionable IMO, as it breaks correct handling of
> scheduling weights on NUMA machines.
> I would suggest to switch this feature off per default and make it a
> configuration option of xend. It would make sense, however, to change cpu pool
> processor allocation to be NUMA-aware.
> Switching NUMA off via boot option would remove NUMA-optimized memory
> allocation, which would be sub-optimal :-)
Hi Jürgen,
stumbled over your mail just now, so sorry for the delay.
First: Don't turn off automatic NUMA placement ;-)
In my tests it helped a lot to preserve performance on NUMA machines.
I was just browsing through the ML archive to find your original CPU
pools description from April, and it seems to fit the requirements in
NUMA machines quite well.
I haven't done any experiments with Cpupools nor haven't looked at the
code yet, but just a quick idea:
What about if we marry static NUMA placement and Cpupools?
I'd suggest to introduce static NUMA pools, one for each node. The CPUs
assigned to each pool are fixed and cannot be removed nor added (because
the NUMA topology is fixed).
Is that possible? Can we assign one physical CPUs to multiple pools (to
Pool-0 and to NUMA-0?) Or are they exclusive or hierarchical like the
Linux' cpusets?
We could introduce magic names for each NUMA pool, so that people just
say cpupool="NUMA-2" and get their domain pinned to that pool. Without
any explicit assignment the system would pick a NUMA node (like it does
today) and would just use the respective Cpupool. I think that is very
similar to what it does today, only that the pinning nature is more
evident to the user (as it uses the Cpupool name space).
Also it would allow for users to override the pinning by specifying a
different Cpupool explicitly (like Pool-0).
Just tell me what you think about this and whether I am wrong with my
thinking ;-)
Regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448-3567-12
next prev parent reply other threads:[~2010-09-27 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 13:38 RFC: automatic NUMA placement Juergen Gross
2010-09-16 15:52 ` Dan Magenheimer
2010-09-17 6:26 ` Juergen Gross
2010-09-27 21:46 ` Andre Przywara [this message]
2010-09-28 4:48 ` Juergen Gross
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=4CA110D3.5050000@amd.com \
--to=andre.przywara@amd.com \
--cc=juergen.gross@ts.fujitsu.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.