linux-kernel - Re: [PATCH 2/5] workqueue: update wq_numa_possible

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20141225201620.GC22951@htj.dyndns.org>
Date:	Thu, 25 Dec 2014 15:16:20 -0500
From:	Tejun Heo <tj@...nel.org>
To:	Lai Jiangshan <laijs@...fujitsu.com>
Cc:	linux-kernel@...r.kernel.org,
	Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>,
	"Gu, Zheng" <guz.fnst@...fujitsu.com>,
	tangchen <tangchen@...fujitsu.com>,
	Hiroyuki KAMEZAWA <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [PATCH 2/5] workqueue: update wq_numa_possible_cpumask

On Mon, Dec 15, 2014 at 10:02:04AM +0800, Lai Jiangshan wrote:
> 1) "NUMA code" = system's NUMA memory hotplug code, AKA, keep the numa mapping stable
> 
>    I think this is the better idea.  This idea came to my mind immediately at the time
>    I received the bug report.  And after some discussions, I was told that it is too HARD
>    to keep the numa mapping stable across multiple physical system-board/node online/offline.

If the arch needs to change it, that's fine, I guess.  What I'm saying
is that we should move this table building and maintenance to numa
code proper.  It was already a bit icky to build it inside workqueue.
Trying to manage it dynamically manage it from there is too ugly.
Let's please make this mapping table a proper part of NUMA
infrastructure with proper notification callbacks.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/