Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753493Ab1DUTdy (ORCPT ); Thu, 21 Apr 2011 15:33:54 -0400 Received: from smtp-out.google.com ([216.239.44.51]:22364 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752719Ab1DUTdw (ORCPT ); Thu, 21 Apr 2011 15:33:52 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version:content-type; b=fkS85yKwWvUS+vVIEnmQNLq7Ru7xRSP7RAL0O3HxYeSOAhOHMMLVCYRpqaS+3OEbUk sXAIvyxXkvLJsKEpsPdQ== Date: Thu, 21 Apr 2011 12:33:46 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: KOSAKI Motohiro cc: James Bottomley , Pekka Enberg , Christoph Lameter , Michal Hocko , Andrew Morton , Hugh Dickins , linux-mm@kvack.org, LKML , linux-parisc@vger.kernel.org, Ingo Molnar , x86 maintainers Subject: Re: [PATCH v3] mm: make expand_downwards symmetrical to expand_upwards In-Reply-To: <20110421221712.9184.A69D9226@jp.fujitsu.com> Message-ID: References: <1303337718.2587.51.camel@mulgrave.site> <20110421221712.9184.A69D9226@jp.fujitsu.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 779 Lines: 18 On Thu, 21 Apr 2011, KOSAKI Motohiro wrote: > 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) > ia64 doesn't enable CONFIG_HIGHMEM, so it never gets set via this generic code; mips also doesn't enable it for all configs even for 32-bit. So we'll either want to take check_for_regular_memory() out from under CONFIG_HIGHMEM and do it for all configs or teach slub to use N_HIGH_MEMORY rather than N_NORMAL_MEMORY. -- 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/