Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 14 Oct 2002 21:06:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 14 Oct 2002 21:06:50 -0400 Received: from holomorphy.com ([66.224.33.161]:62354 "EHLO holomorphy") by vger.kernel.org with ESMTP id ; Mon, 14 Oct 2002 21:06:49 -0400 Date: Mon, 14 Oct 2002 18:08:59 -0700 From: William Lee Irwin III To: john stultz Cc: Matt , "Martin J. Bligh" , "Eric W. Biederman" , linux-kernel , linux-mm@kvack.org, LSE Tech , Andrew Morton , Michael Hohnbaum Subject: Re: [Lse-tech] Re: [rfc][patch] Memory Binding API v0.3 2.5.41 Message-ID: <20021015010859.GM4488@holomorphy.com> Mail-Followup-To: William Lee Irwin III , john stultz , Matt , "Martin J. Bligh" , "Eric W. Biederman" , linux-kernel , linux-mm@kvack.org, LSE Tech , Andrew Morton , Michael Hohnbaum References: <3DAB5DF2.5000002@us.ibm.com> <2004595005.1034616026@[10.10.2.3]> <3DAB6385.9000207@us.ibm.com> <1034643354.19094.149.camel@cog> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1034643354.19094.149.camel@cog> User-Agent: Mutt/1.3.25i Organization: The Domain of Holomorphy Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1376 Lines: 28 On Mon, 2002-10-14 at 17:38, Matthew Dobson wrote: >> Also, right now, memblks map to nodes in a straightforward manner (1-1 >> on NUMA-Q, the only architecture that has defined them). It will likely >> look the same on most architectures, too. On Mon, Oct 14, 2002 at 05:55:53PM -0700, john stultz wrote: > Just an FYI: I believe the x440 breaks this assumption. > There are 2 chunks on the first CEC. The current discontig patch for it > has to drop the second chunk (anything over 3.5G on the first CEC) in > order to work w/ the existing code. However, that will probably need to > be addressed at some point, so be aware that this might affect you as > well. MAP_NR_DENSE()-based zone-relative pfn to zone->zone_mem_map index remapping is designed to handle this (and actually more severe situations). The only constraint is that pfn's must be monotonically increasing with ->zone_mem_map index. Some non-i386 architectures virtually remap physical memory to provide the illusion of contiguity of kernel virtual memory, but in a mature port (e.g. i386) there's high risk of breaking numerous preexisting drivers. Bill - 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/