From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932098AbbCCNS6 (ORCPT ); Tue, 3 Mar 2015 08:18:58 -0500 Received: from mail-qg0-f43.google.com ([209.85.192.43]:55823 "EHLO mail-qg0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756210AbbCCNS5 (ORCPT ); Tue, 3 Mar 2015 08:18:57 -0500 Date: Tue, 3 Mar 2015 08:18:52 -0500 From: Tejun Heo To: Kamezawa Hiroyuki Cc: Gu Zheng , linux-kernel@vger.kernel.org, laijs@cn.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com, tangchen@cn.fujitsu.com Subject: Re: [PATCH] workqueue: update numa affinity when node hotplug Message-ID: <20150303131852.GA3122@htj.duckdns.org> References: <1425031492-32300-1-git-send-email-guz.fnst@cn.fujitsu.com> <20150227115401.GD3964@htj.duckdns.org> <54F42221.6000904@jp.fujitsu.com> <20150302162854.GG17694@htj.duckdns.org> <54F55A7A.7060100@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54F55A7A.7060100@jp.fujitsu.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, Kame. On Tue, Mar 03, 2015 at 03:53:46PM +0900, Kamezawa Hiroyuki wrote: > relationship between proximity domain and lapic id doesn't change. > relationship between lapic-id and cpu-id changes. > > pxm <-> memory address : no change > pxm <-> lapicid : no change > pxm <-> node id : no change > lapicid <-> cpu id : change. So, we're changing the cpu ID to NUMA node mapping because current NUMA code is ignoring PXM for memoryless nodes? That's it? > >>I personally thinks proper fix is building persistent cpu-id <-> lapicid relationship as > >>pxm does rather than creating band-aid. > > > >Oh if this is possible, I agree that's the right direction too. > > > > Implementation is a bit complicated now :(. Ah well, even then, the obviously right thing to do is updating NUMA code to always keep track of PXM information. We don't really want to pile NUMA hacks in random users of NUMA code. Thanks. -- tejun