From: Peter Zijlstra <peterz@infradead.org>
To: riel@redhat.com
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org, mgorman@suse.de,
chegu_vinod@hp.com
Subject: Re: [PATCH 1/4] numa,x86: store maximum numa node distance
Date: Fri, 9 May 2014 11:45:43 +0200 [thread overview]
Message-ID: <20140509094543.GP30445@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1399569811-14362-2-git-send-email-riel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
On Thu, May 08, 2014 at 01:23:28PM -0400, riel@redhat.com wrote:
> From: Rik van Riel <riel@redhat.com>
>
> Store the maximum node distance, so the numa placement code can do
> better placement on systems with complex numa topology.
>
> The function max_node_distance will return LOCAL_DISTANCE if the
> system has simple NUMA topology, with only a single level of
> remote distance.
>
> Signed-off-by: Rik van Riel <riel@redhat.com>
> Tested-by: Chegu Vinod <chegu_vinod@hp.com>
> ---
> arch/x86/include/asm/topology.h | 3 +++
> arch/x86/mm/numa.c | 25 +++++++++++++++++++++++++
> include/linux/topology.h | 3 +++
> 3 files changed, 31 insertions(+)
>
Why are you doing this in arch code? I would've expected some extra code
to sched_init_numa() which is generic code that analyses the distance
table and reconstructs the actual topology from it.
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-09 9:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 17:23 [PATCH 0/4] sched,numa: task placement for complex NUMA topologies riel
2014-05-08 17:23 ` [PATCH 1/4] numa,x86: store maximum numa node distance riel
2014-05-09 9:45 ` Peter Zijlstra [this message]
2014-05-09 15:08 ` Rik van Riel
2014-05-08 17:23 ` [PATCH 2/4] sched,numa: weigh nearby nodes for task placement on complex NUMA topologies riel
2014-05-09 9:53 ` Peter Zijlstra
2014-05-09 15:14 ` Rik van Riel
2014-05-09 9:54 ` Peter Zijlstra
2014-05-09 10:03 ` Peter Zijlstra
2014-05-09 15:16 ` Rik van Riel
2014-05-09 10:11 ` Peter Zijlstra
2014-05-09 15:11 ` Rik van Riel
2014-05-09 10:13 ` Peter Zijlstra
2014-05-09 15:03 ` Rik van Riel
2014-05-08 17:23 ` [PATCH 3/4] sched,numa: store numa_group's preferred nid riel
2014-05-08 17:23 ` [PATCH 4/4] sched,numa: pull workloads towards their preferred nodes riel
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=20140509094543.GP30445@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=chegu_vinod@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=riel@redhat.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).