From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] numa: fix problems with memory-less nodes
Date: Wed, 13 Jan 2010 10:02:30 +0000 [thread overview]
Message-ID: <C7734AB6.63FE%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4B4D9582.5010806@amd.com>
On 13/01/2010 09:42, "Andre Przywara" <andre.przywara@amd.com> wrote:
> node_to_cpu : node0:0-5,24-35
> node1:6-11
> node2:12-17
> node3:18-23
> node4:no cpus
> node5:no cpus
> node_to_memory : node0:14267
> node1:8167
> node2:16335
> node3:8167
> node4:0
> node5:0
To be clear: I certainly agree that node_to_cpu[4,5] should list the CPUs
that are present, even if the nodes are memory-less. But you tell me how
20762 has changed this behaviour.
If it was changed by one of Intel's slightly earlier changesets (which is
possible) I'm happy to see it changed back. The new node_to_cpu[] behaviour
you are observing is obviously stupid, and I assume unintended.
-- Keir
prev parent reply other threads:[~2010-01-13 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 16:30 [PATCH] numa: fix problems with memory-less nodes Andre Przywara
2010-01-13 8:26 ` Keir Fraser
2010-01-13 9:42 ` Andre Przywara
2010-01-13 9:55 ` Keir Fraser
2010-01-13 10:02 ` Keir Fraser [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=C7734AB6.63FE%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=andre.przywara@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).