linux-mips
[Top] [All Lists]

Re: mips32 kernel memory mapping

To: Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: mips32 kernel memory mapping
From: Ralf Baechle <ralf@linux-mips.org>
Date: Sat, 24 Jul 2004 02:32:44 +0200
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>, Srinivas Kommu <kommu@hotmail.com>, Linux/MIPS Development <linux-mips@linux-mips.org>
In-reply-to: <Pine.GSO.4.58.0407232233430.13094@waterleaf.sonytel.be>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <BAY1-F25sCR6nWqNG2Y00092cf9@hotmail.com> <Pine.LNX.4.58L.0407231348580.5644@blysk.ds.pg.gda.pl> <20040723202439.GA3711@linux-mips.org> <Pine.GSO.4.58.0407232233430.13094@waterleaf.sonytel.be>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i
On Fri, Jul 23, 2004 at 10:34:35PM +0200, Geert Uytterhoeven wrote:

> On Fri, 23 Jul 2004, Ralf Baechle wrote:
> > There are still improvments to be made for BCM1250 support.  Somebody
> > thought scattering the first 1GB of memory through the lowest 4GB of
> > physical address space like a three year old his toys over the floor
> > was a good thing ...  The resulting holes in the memory map are wasting
> > significant amounts of memory for unused memory; the worst case number
> > that is reached for 64-bit kernel on a system with > 1GB of RAM is 96MB!
> 
> Perhaps you want to start using virtually mapped zones, like m68k?

We could do that, yes.  In the cases that would gain most such as the
BCM1250 it'd not be possible though - there simply is not enough virtual
address space left in KSEG2/3.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>