From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753246AbbCZPTK (ORCPT ); Thu, 26 Mar 2015 11:19:10 -0400 Received: from mail-qg0-f53.google.com ([209.85.192.53]:35219 "EHLO mail-qg0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752200AbbCZPTH (ORCPT ); Thu, 26 Mar 2015 11:19:07 -0400 Date: Thu, 26 Mar 2015 11:18:50 -0400 From: Tejun Heo To: Gu Zheng Cc: Kamezawa Hiroyuki , linux-kernel@vger.kernel.org, laijs@cn.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com, tangchen@cn.fujitsu.com, izumi.taku@jp.fujitsu.com Subject: Re: [PATCH 0/2] workqueue: fix a bug when numa mapping is changed Message-ID: <20150326151850.GD1953@htj.duckdns.org> References: <1427336275-32066-1-git-send-email-guz.fnst@cn.fujitsu.com> <55137935.5080301@jp.fujitsu.com> <55139340.8070201@cn.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55139340.8070201@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 Hello, On Thu, Mar 26, 2015 at 01:04:00PM +0800, Gu Zheng wrote: > wq generates the numa affinity (pool->node) for all the possible cpu's > per cpu workqueue at init stage, that means the affinity of currently un-present > ones' may be incorrect, so we need to update the pool->node for the new added cpu > to the correct node when preparing online, otherwise it will try to create worker > on invalid node if node hotplug occurred. If the mapping is gonna be static once the cpus show up, any chance we can initialize that for all possible cpus during boot? Thanks. -- tejun