Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Jun Sun <jsun@mvista.com>
Cc: Daniel Jacobowitz <dan@debian.org>,
	Matthew Dharm <mdharm@momenco.com>,
	Linux-MIPS <linux-mips@oss.sgi.com>
Subject: Re: MIPS 64?
Date: Wed, 15 May 2002 23:28:18 -0400	[thread overview]
Message-ID: <3CE32752.80109@embeddededge.com> (raw)
In-Reply-To: 3CE2DA46.3070402@mvista.com

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

  parent reply	other threads:[~2002-05-16  3:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15 21:34 MIPS 64? Matthew Dharm
2002-05-15 21:48 ` Daniel Jacobowitz
2002-05-15 21:55   ` Kip Walker
2002-05-15 22:08     ` Matthew Dharm
2002-05-15 22:08       ` Matthew Dharm
2002-05-15 22:15       ` Kip Walker
2002-05-15 22:26         ` Matthew Dharm
2002-05-15 22:29           ` Kip Walker
2002-05-19 19:29           ` Ralf Baechle
2002-05-19 19:25       ` Ralf Baechle
2002-05-15 21:59   ` Jun Sun
2002-05-15 22:16     ` Matthew Dharm
2002-05-19 19:32       ` Ralf Baechle
2002-05-16  3:28     ` Dan Malek [this message]
2002-05-16  7:15     ` Kevin D. Kissell
2002-05-16 17:13       ` Jun Sun
2002-05-19 19:44         ` Ralf Baechle
2002-05-19 19:41       ` Ralf Baechle
2002-05-19 19:30     ` Ralf Baechle
2002-05-20 10:06       ` Maciej W. Rozycki
2002-05-20 15:57         ` Greg Lindahl
2002-05-20 16:05           ` Maciej W. Rozycki
2002-05-21 16:47           ` Florian Lohoff
2002-05-21 17:00             ` Greg Lindahl
2002-05-20 19:05         ` Ralf Baechle
2002-05-19 19:24   ` Ralf Baechle
2002-05-19 19:23 ` Ralf Baechle
2002-05-20  6:05   ` Matthew Dharm
2002-05-20 20:30     ` Ralf Baechle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3CE32752.80109@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=dan@debian.org \
    --cc=jsun@mvista.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=mdharm@momenco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox