From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Valentin Schneider <valentin.schneider@arm.com>
Cc: "Peter Zijlstra (Intel)" <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
Sergei Trofimovich <slyfox@gentoo.org>,
debian-ia64 <debian-ia64@lists.debian.org>
Subject: Re: [PATCH 0/1] sched/topology: NUMA distance deduplication
Date: Thu, 18 Mar 2021 00:26:28 +0100 [thread overview]
Message-ID: <132937a8-0514-5a62-2897-569187e355a7@physik.fu-berlin.de> (raw)
In-Reply-To: <87wnu5pkib.mognet@arm.com>
Hi Valentin!
On 3/17/21 9:56 PM, Valentin Schneider wrote:
> On 17/03/21 20:04, Valentin Schneider wrote:
>> Technically it *is* coping with it, it's just dumping the entire NUMA
>> distance matrix in the process... Let me see if I can't figure out why your
>> system doesn't end up with nr_node_ids=1.
>>
>
> Does the below
> a) compile
Yes.
> b) do anything?
It fixes the problem for me.
Will test Sergei's patch now.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2021-03-17 23:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 19:04 [PATCH 0/1] sched/topology: NUMA distance deduplication John Paul Adrian Glaubitz
2021-03-17 19:36 ` Valentin Schneider
2021-03-17 19:47 ` John Paul Adrian Glaubitz
2021-03-17 20:04 ` Valentin Schneider
2021-03-17 20:56 ` Valentin Schneider
2021-03-17 23:26 ` John Paul Adrian Glaubitz [this message]
2021-03-18 10:28 ` John Paul Adrian Glaubitz
2021-03-18 10:48 ` Valentin Schneider
2021-03-17 21:14 ` Sergei Trofimovich
2021-03-17 21:58 ` Anatoly Pugachev
2021-03-17 23:29 ` John Paul Adrian Glaubitz
-- strict thread matches above, loose matches on Subject: below --
2021-01-22 12:39 Valentin Schneider
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=132937a8-0514-5a62-2897-569187e355a7@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-ia64@lists.debian.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=slyfox@gentoo.org \
--cc=valentin.schneider@arm.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).