Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761593AbaGRLUo (ORCPT ); Fri, 18 Jul 2014 07:20:44 -0400 Received: from mail-qg0-f43.google.com ([209.85.192.43]:42098 "EHLO mail-qg0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755880AbaGRLUm (ORCPT ); Fri, 18 Jul 2014 07:20:42 -0400 Date: Fri, 18 Jul 2014 07:20:39 -0400 From: Tejun Heo To: Nishanth Aravamudan Cc: benh@kernel.crashing.org, Joonsoo Kim , David Rientjes , Wanpeng Li , Jiang Liu , Tony Luck , Fenghua Yu , linux-ia64@vger.kernel.org, linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org Subject: Re: [RFC 0/2] Memoryless nodes and kworker Message-ID: <20140718112039.GA8383@htj.dyndns.org> References: <20140717230923.GA32660@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140717230923.GA32660@linux.vnet.ibm.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 On Thu, Jul 17, 2014 at 04:09:23PM -0700, Nishanth Aravamudan wrote: > [Apologies for the large Cc list, but I believe we have the following > interested parties: > > x86 (recently posted memoryless node support) > ia64 (existing memoryless node support) > ppc (existing memoryless node support) > previous discussion of how to solve Anton's issue with slab usage > workqueue contributors/maintainers] Well, you forgot to cc me. ... > It turns out we see this large slab usage due to using the wrong NUMA > information when creating kthreads. > > Two changes are required, one of which is in the workqueue code and one > of which is in the powerpc initialization. Note that ia64 may want to > consider something similar. Wasn't there a thread on this exact subject a few weeks ago? Was that someone else? Memory-less node detail leaking out of allocator proper isn't a good idea. Please allow allocator users to specify the nodes they're on and let the allocator layer deal with mapping that to whatever is appropriate. Please don't push that to everybody. 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/