Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752654AbaA2P6J (ORCPT ); Wed, 29 Jan 2014 10:58:09 -0500 Received: from qmta09.emeryville.ca.mail.comcast.net ([76.96.30.96]:53058 "EHLO qmta09.emeryville.ca.mail.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751477AbaA2P6H (ORCPT ); Wed, 29 Jan 2014 10:58:07 -0500 Date: Wed, 29 Jan 2014 09:58:04 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@nuc To: David Rientjes cc: Nishanth Aravamudan , LKML , Anton Blanchard , Andrew Morton , Tejun Heo , Oleg Nesterov , Jan Kara , Thomas Gleixner , Tetsuo Handa , linux-mm@kvack.org, Wanpeng Li , Joonsoo Kim , Ben Herrenschmidt Subject: Re: [PATCH] kthread: ensure locality of task_struct allocations In-Reply-To: Message-ID: References: <20140128183808.GB9315@linux.vnet.ibm.com> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 29 Jan 2014, David Rientjes wrote: > > diff --git a/kernel/kthread.c b/kernel/kthread.c > > index b5ae3ee..8573e4e 100644 > > --- a/kernel/kthread.c > > +++ b/kernel/kthread.c > > @@ -217,7 +217,7 @@ int tsk_fork_get_node(struct task_struct *tsk) > > if (tsk == kthreadd_task) > > return tsk->pref_node_fork; > > #endif > > - return numa_node_id(); > > + return numa_mem_id(); > > I'm wondering why return NUMA_NO_NODE wouldn't have the same effect and > prefer the local node? > The idea here seems to be that the allocation may occur from a cpu that is different from where the process will run later on. -- 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/