Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755003Ab1DUQhb (ORCPT ); Thu, 21 Apr 2011 12:37:31 -0400 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:36125 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754912Ab1DUQha (ORCPT ); Thu, 21 Apr 2011 12:37:30 -0400 Subject: Re: [PATCH v3] mm: make expand_downwards symmetrical to expand_upwards From: James Bottomley To: KOSAKI Motohiro Cc: David Rientjes , Pekka Enberg , Christoph Lameter , Michal Hocko , Andrew Morton , Hugh Dickins , linux-mm@kvack.org, LKML , linux-parisc@vger.kernel.org, Ingo Molnar , x86 maintainers In-Reply-To: <20110421221712.9184.A69D9226@jp.fujitsu.com> References: <1303337718.2587.51.camel@mulgrave.site> <20110421221712.9184.A69D9226@jp.fujitsu.com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 21 Apr 2011 11:37:27 -0500 Message-ID: <1303403847.4025.11.camel@mulgrave.site> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1048 Lines: 25 On Thu, 2011-04-21 at 22:16 +0900, KOSAKI Motohiro wrote: > > This should fix the remaining architectures so they can use CONFIG_SLUB, > > but I hope it can be tested by the individual arch maintainers like you > > did for parisc. > > ia64 and mips have CONFIG_ARCH_POPULATES_NODE_MAP and it initialize > N_NORMAL_MEMORY automatically if my understand is correct. > (plz see free_area_init_nodes) > > I guess alpha and m32r have no active developrs. only m68k seems to be need > fix and we have a chance to get a review... Actually, it's not quite a fix yet, I'm afraid. I've just been investigating why my main 4 way box got slower with kernel builds: Apparently userspace processes are now all stuck on CPU0, so we're obviously tripping over some NUMA scheduling stuff that's missing. James -- 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/