From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 2 May 2002 15:30:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 2 May 2002 15:30:01 -0400 Received: from e21.nc.us.ibm.com ([32.97.136.227]:15315 "EHLO e21.nc.us.ibm.com") by vger.kernel.org with ESMTP id ; Thu, 2 May 2002 15:29:17 -0400 To: Andrea Arcangeli cc: "Martin J. Bligh" , Daniel Phillips , Russell King , linux-kernel@vger.kernel.org Reply-To: Gerrit Huizenga From: Gerrit Huizenga Subject: Re: Bug: Discontigmem virt_to_page() [Alpha,ARM,Mips64?] In-Reply-To: Your message of Thu, 02 May 2002 20:10:43 +0200. <20020502201043.L11414@dualathlon.random> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7982.1020367732.1@us.ibm.com> Date: Thu, 02 May 2002 12:28:52 -0700 Message-Id: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org In message <20020502201043.L11414@dualathlon.random>, > : Andrea Arcangeli writ es: > On Thu, May 02, 2002 at 09:58:02AM -0700, Gerrit Huizenga wrote: > > In message <3971861785.1020330424@[10.10.2.3]>, > : "Martin J. Bligh" writes: > > > > With numa-q there's a 512M hole in each node IIRC. that's fine > > > > configuration, similar to the wildfire btw. > > > > > > There's 2 different memory models - the NT mode we use currently > > > is contiguous, the PTX mode is discontiguous. I don't think it's > > > as simple as a 512Mb fixed size hole, though I'd have to look it > > > up to be sure. > > > > No - it definitely isn't as simple as a 512 MB hole. Depends on how much > > I meant that as an example, I recall that was valid config, 512M of ram > and 512M hole, then next node 512M ram and 512M hole etc... Of course it > must be possible to vary the mem size if you want more or less ram in > each node but still it doesn't generate a problematic layout for > discontigmem (i.e. not 256 discontigous chunks or something of that > order). I *think* the ranges were typically aligned to 4 GB, although with 8 GB in a single node, I don't remember what the mapping layout looked like. Which made everything but node 0 into HIGHMEM. With the "flat" addressing mode that Martin has been using (the dummied down for NT version) everything is squished together. That makes it a bit harder to do node local data structures, although he may have enough data from the MPS table to split memory appropriately. gerrit