All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"yunhong.jiang@intel.com" <yunhong.jiang@intel.com>
Subject: Re: [PATCH] xend: Fix non-contiguous NUMA node assignment
Date: Mon, 18 Jan 2010 09:53:04 +0100	[thread overview]
Message-ID: <4B542170.6000202@amd.com> (raw)
In-Reply-To: <C7790DAE.6779%keir.fraser@eu.citrix.com>

Keir Fraser wrote:
> I had a go myself: see c/s 20817. This keeps nr_nodes as well as
> max_node_id, and continues to use it where it seemed to make sense to do so.

c/s 20817 seems OK to me. Actually that was how I started, but then 
decided to drop max_node_id because I didn't see the sense in keeping 
two variables which actually differ just by 1. But I didn't consider 
chunk #3 of XendDomainInfo.py, which actually also fixes another bug.

Thanks!
Regards,
Andre.

> 
>  -- Keir
> 
> On 17/01/2010 17:48, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:
> 
>> nr_nodes was always num_online_nodes() returned by Xen -- not accounting for
>> holes in node id space. Hance I emulated that behaviour from the Python
>> extension package. If what you actually want everywhere in the Python code
>> is max_node_id, then please remove the nr_nodes code from xc.c and all
>> references to it from the Python code. I agree that using max_node_id seems
>> more correct than nr_nodes -- the intention was for someone to plumb that
>> new field properly into the Python code anyway.
>>
>>  -- Keir
>>
>> On 15/01/2010 13:28, "Andre Przywara" <andre.przywara@amd.com> wrote:
>>
>>> Hi,
>>>
>>> it seems that I missed a point in this whole addition of max_node_id. I
>>> see the difference in the Xen HV part, so nr_nodes got replaced with
>>> max_node_id in physinfo_t (and xc_physinfo_t, respectively).
>>> But where does this value help in xend? There is no single Python
>>> reference to the physinfo()'s max_node_id field, instead all functions
>>> use the old (but now bogus) nr_nodes variable.
>>> So in the attached patch I kept the xc.physinfo() returned dictionary
>>> with only a nr_nodes field, calculated by simply adding 1 to max_node_id
>>> from libxc. Empty nodes can (and will) be detected by iterating through
>>> the node_to_cpus and node_to_memory lists.
>>> Nodes without memory should not be considered during guest's memory
>>> allocation, but will be used for further CPU affinity setting if the
>>> number of VCPUs exceeds the number of cores per node.
>>>
>>> Please correct me if I am totally wrong on this, but this seems to work
>>> much better in my case.
>>>
>>> Regards,
>>> Andre.
>>>
>>> Signed-off-by: Andre Przywara <andre.przywara@amd.com>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> 
> 

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 488-3567-12
----to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Andrew Bowd; Thomas M. McCoy; Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2010-01-18  8:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-15 13:28 [PATCH] xend: Fix non-contiguous NUMA node assignment Andre Przywara
2010-01-17  2:10 ` Jiang, Yunhong
2010-01-17 17:48 ` Keir Fraser
2010-01-17 18:55   ` Keir Fraser
2010-01-18  8:53     ` Andre Przywara [this message]
2010-01-18  9:19       ` Keir Fraser

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=4B542170.6000202@amd.com \
    --to=andre.przywara@amd.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yunhong.jiang@intel.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.