linux-mips
[Top] [All Lists]

Re: MIPS 64?

To: Jun Sun <jsun@mvista.com>
Subject: Re: MIPS 64?
From: Dan Malek <dan@embeddededge.com>
Date: Wed, 15 May 2002 23:28:18 -0400
Cc: Daniel Jacobowitz <dan@debian.org>, Matthew Dharm <mdharm@momenco.com>, Linux-MIPS <linux-mips@oss.sgi.com>
Organization: Embedded Edge, LLC.
References: <NEBBLJGMNKKEEMNLHGAIOEPPCGAA.mdharm@momenco.com> <20020515214818.GA1991@nevyn.them.org> <3CE2DA46.3070402@mvista.com>
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:0.9.9) Gecko/20020411
Jun Sun wrote:

So you really can't do 1.5GB on 32 bit kernel.

It is interesting that PPC allows one to adjust user space size and kernel space size. So on PPC you can get up to 2.5GB system RAM with 1GB user space.

Don't be confusing virtual/physical addressing.  The highmem stuff allows
access to larger physical address space by providing "windows" through
the virtual space.  The memory space configuration on PPC was done before
highmem was working properly, but it has remained as an embedded configuration
option.  When using highmem, you obviously can't map all of the physical
memory at once, so your applications and drivers have to coordinate what
is mapped at a single instance.  The PPC configuration option gives us a
little flexibility to allow a little more kernel mapping for drivers when
it is necessary (or to work around weird I/O mapping problems).

Thanks.


        -- Dan


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