Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753946AbbGWSce (ORCPT ); Thu, 23 Jul 2015 14:32:34 -0400 Received: from mail-yk0-f172.google.com ([209.85.160.172]:35901 "EHLO mail-yk0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753070AbbGWScc (ORCPT ); Thu, 23 Jul 2015 14:32:32 -0400 Date: Thu, 23 Jul 2015 14:32:28 -0400 From: Tejun Heo To: Tang Chen Cc: mingo@redhat.com, akpm@linux-foundation.org, rjw@rjwysocki.net, hpa@zytor.com, laijs@cn.fujitsu.com, yasu.isimatu@gmail.com, isimatu.yasuaki@jp.fujitsu.com, kamezawa.hiroyu@jp.fujitsu.com, izumi.taku@jp.fujitsu.com, gongzhaogang@inspur.com, qiaonuohan@cn.fujitsu.com, x86@kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH 0/5] Make cpuid <-> nodeid mapping persistent. Message-ID: <20150723183228.GR15934@mtj.duckdns.org> References: <1436261425-29881-1-git-send-email-tangchen@cn.fujitsu.com> <20150715221345.GO15934@mtj.duckdns.org> <55B07145.5010404@cn.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55B07145.5010404@cn.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 Content-Length: 1035 Lines: 28 Hello, Tang. On Thu, Jul 23, 2015 at 12:44:53PM +0800, Tang Chen wrote: > Allocating cpuid when a new cpu comes up and reusing the cpuid when it > comes up again is possible. But I'm not quite sure if it will be less > modification > because we still need an array or bit map or something to keep the mapping, > and select backup nodes for cpus on memory-less nodes when allocating > memory. > > I can post a set of patches for this idea. And then we can see which one is > better. I suspect the difference could be that in the current code the users (workqueue) can remain the same while if we do it lazily there probably needs to be a way to poke it. As long as the IDs are allocated to the online CPUs first, I think pre-allocating everything should be fine too. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/