This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Thu Apr 25 18:39:31 2024 Received: from spaans.ds9a.nl (adsl-xs4all.ds9a.nl [213.84.159.51]) by kylie.puddingonline.com (8.11.6/8.11.6) with SMTP id g8IL0sX23389 for ; Wed, 18 Sep 2002 23:00:54 +0200 Received: (qmail 7959 invoked from network); 18 Sep 2002 08:05:07 -0000 Received: from unknown (HELO spaans.ds9a.nl) (3ffe:8280:10:360:202:44ff:fe2a:a1dd) by mayo.ipv6.ds9a.nl with SMTP; 18 Sep 2002 08:05:07 -0000 Received: (qmail 23410 invoked by uid 1000); 17 Sep 2002 21:28:43 -0000 Received: (maildatabase); juh Received: (qmail 1744 invoked by alias); 6 May 2002 05:42:51 -0000 Received: (qmail 1741 invoked from network); 6 May 2002 05:42:51 -0000 Received: from unknown (HELO mayo.ds9a.nl) (::ffff:10.0.0.202) by ::ffff:10.0.0.8 with SMTP; 6 May 2002 05:42:51 -0000 Received: (qmail 19120 invoked from network); 6 May 2002 01:42:47 -0000 Received: from unknown (HELO dipsaus.ds9a.tudelft.nl) (3ffe:8280:10:360:2a0:cff:fe14:9dde) by mayo.ipv6.ds9a.nl with SMTP; 6 May 2002 01:42:47 -0000 Received: (qmail 31186 invoked from network); 6 May 2002 01:42:43 -0000 Received: from unknown (HELO vger.kernel.org) (::ffff:209.116.70.75) by adsl-xs4all.ds9a.nl with SMTP; 6 May 2002 01:42:43 -0000 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 5 May 2002 21:41:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 5 May 2002 21:41:18 -0400 Received: from [195.223.140.120] ([195.223.140.120]:44842 "EHLO penguin.e-mind.com") by vger.kernel.org with ESMTP id ; Sun, 5 May 2002 21:41:17 -0400 Received: from black.random (cda1.e-mind.com [195.223.140.107] (may be forged)) by penguin.e-mind.com (8.9.1a/8.9.1/Debian/GNU) with ESMTP id EAA11649; Mon, 6 May 2002 04:02:16 +0200 Received: from dualathlon.random (dualathlon.random [192.168.1.12]) by black.random (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) with ESMTP id g461fVZ03323; Mon, 6 May 2002 03:41:31 +0200 Received: (from andrea@localhost) by dualathlon.random (8.11.6/8.11.6/SuSE Linux 0.5) id g461gIh02998; Mon, 6 May 2002 03:42:18 +0200 Date: Mon, 6 May 2002 03:42:18 +0200 From: Andrea Arcangeli To: Daniel Phillips Cc: Russell King , "Martin J. Bligh" , linux-kernel@vger.kernel.org Subject: Re: Bug: Discontigmem virt_to_page() [Alpha,ARM,Mips64?] Message-Id: <20020506034218.H6712@dualathlon.random> References: <20020502180632.I11414@dualathlon.random> <20020506032054.F6712@dualathlon.random> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i X-GnuPG-Key-URL: http://e-mind.com/~andrea/aa.gnupg.asc X-PGP-Key-URL: http://e-mind.com/~andrea/aa.asc Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org X-Spam-Status: No, hits=-3.1 required=6.0 tests=IN_REP_TO,MAY_BE_FORGED version=2.20 X-Spam-Level: Lines: 86 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, May 06, 2002 at 03:24:58AM +0200, Daniel Phillips wrote: > On Monday 06 May 2002 03:20, Andrea Arcangeli wrote: > > On Mon, May 06, 2002 at 03:07:07AM +0200, Daniel Phillips wrote: > > > On Monday 06 May 2002 02:55, Russell King wrote: > > > So, since __phys_to_virt (and hence phys_to_virt and __va) is clearly linear, the > > > relation __pa(__va(kva)) == kva cannot hold. Perhaps that doesn't bother you? > > > > Check my previous email: > > > > [..] They will all be normal zones provided you implement a static > > view of them in the kernel virtual address space, and you also > > cover page_address/virt_to_page [..] > > > > Depending on the kind of coalescing of those chunks in the direct > > mapping virt_to_page/page_address will vary. virt_to_page and > > page_address will have all the necessary internal knowledge in order to > > make it all zone_normal. > > What do you mean by 'implement a static view of them'? See the attached email. assuming chunks of 256M ram every 1G, 1G phys goes at 3G+256M virt, 2G goes at 3G+512M etc... Andrea --ZGiS0Q5IWpPtfppv Content-Type: message/rfc822 Content-Disposition: inline Date: Thu, 2 May 2002 18:06:32 +0200 From: Andrea Arcangeli To: Daniel Phillips Cc: "Martin J. Bligh" , Russell King , linux-kernel@vger.kernel.org Subject: Re: Bug: Discontigmem virt_to_page() [Alpha,ARM,Mips64?] Message-ID: <20020502180632.I11414@dualathlon.random> References: <20020502153402.A11414@dualathlon.random> <3968942217.1020327505@[10.10.2.3]> <20020502173522.F11414@dualathlon.random> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i X-GnuPG-Key-URL: http://e-mind.com/~andrea/aa.gnupg.asc X-PGP-Key-URL: http://e-mind.com/~andrea/aa.asc On Wed, May 01, 2002 at 05:42:40PM +0200, Daniel Phillips wrote: > On Thursday 02 May 2002 17:35, Andrea Arcangeli wrote: > > On Thu, May 02, 2002 at 08:18:33AM -0700, Martin J. Bligh wrote: > > > At the moment I use the contig memory model (so we only use discontig for > > > NUMA support) but I may need to change that in the future. > > > > I wasn't thinking at numa-q, but regardless numa-Q fits perfectly into > > the current discontigmem-numa model too as far I can see. > > No it doesn't. The config_discontigmem model forces all zone_normal memory > to be on node zero, so all the remaining nodes can only have highmem locally. You can trivially map the phys mem between 1G and 1G+256M to be in a direct mapping between 3G+256M and 3G+512M, then you can put such 256M at offset 1G into the ZONE_NORMAL of node-id 1 with discontigmem too. The constraints you have on the normal memory are only two: 1) direct mapping 2) DMA so as far as the ram is capable of 32bit DMA with pci32 and it's mapped in the direct mapping you can put it into the normal zone. There is no difference at all between discontimem or nonlinear in this sense. > Even with good cache hardware, this has to hurt. Andrea --ZGiS0Q5IWpPtfppv-- - 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/