[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160519144657.GK3206@twins.programming.kicks-ass.net>
Date: Thu, 19 May 2016 16:46:57 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Zhu Guihua <zhugh.fnst@...fujitsu.com>
Cc: cl@...ux.com, tj@...nel.org, mika.j.penttila@...il.com,
mingo@...hat.com, akpm@...ux-foundation.org, rjw@...ysocki.net,
hpa@...or.com, yasu.isimatu@...il.com,
isimatu.yasuaki@...fujitsu.com, kamezawa.hiroyu@...fujitsu.com,
izumi.taku@...fujitsu.com, gongzhaogang@...pur.com,
len.brown@...el.com, lenb@...nel.org, tglx@...utronix.de,
chen.tang@...ystack.cn, rafael@...nel.org, x86@...nel.org,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH v7 0/5] Make cpuid <-> nodeid mapping persistent
On Thu, May 19, 2016 at 06:39:41PM +0800, Zhu Guihua wrote:
> [Problem]
>
> cpuid <-> nodeid mapping is firstly established at boot time. And workqueue caches
> the mapping in wq_numa_possible_cpumask in wq_numa_init() at boot time.
>
> When doing node online/offline, cpuid <-> nodeid mapping is established/destroyed,
> which means, cpuid <-> nodeid mapping will change if node hotplug happens. But
> workqueue does not update wq_numa_possible_cpumask.
So why are you not fixing up wq_numa_possible_cpumask instead? That
seems the far easier solution.
Do all the other archs that support NUMA and HOTPLUG have the mapping
stable, or will you now go fix each and every one of them?
Powered by blists - more mailing lists