linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Daniel Blakeley <daniel@msc.cornell.edu>
Cc: linux-mm@kvack.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: Large memory system
Date: Mon, 8 Feb 1999 11:22:15 GMT	[thread overview]
Message-ID: <199902081122.LAA02263@dax.scot.redhat.com> (raw)
In-Reply-To: <19990130083631.B9427@msc.cornell.edu>

Hi,

On Sat, 30 Jan 1999 08:36:31 -0500, Daniel Blakeley
<daniel@msc.cornell.edu> said:

> I've jumped the gun a little bit and recommended a Professor buy 4GB
> of RAM on a Xeon machine to run Linux on and he did.  After he got it
> I read the large memory howto which states that the max memory size
> for Linux 2.2.x is 2GB physical/2GB virtual.  The memory size seems to
> limited by the 32bit nature of the x86 architecture.  The Xeon seems
> to have a 36bit memory addressing mode.  Can Linux be easily expanded
> to use the 36bit addressing?

It's not exactly trivial, but it can (and will) be done.  For now, you
can only use 4G on a 64-bit architecture (Alpha or Sparc64), but
basically we know how to address it on Intel too, transparently to the
user.

--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/

  parent reply	other threads:[~1999-02-08 11:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-30 13:36 Daniel Blakeley
1999-01-30 17:00 ` Benjamin C.R. LaHaise
1999-02-08 11:24   ` Stephen C. Tweedie
1999-02-08 15:31     ` Eric W. Biederman
1999-02-09 22:57       ` Stephen C. Tweedie
1999-02-01 15:59 ` Rik van Riel
1999-02-08 11:22 ` Stephen C. Tweedie [this message]
1999-02-08 20:33 Manfred Spraul
1999-02-10 14:25 ` Stephen C. Tweedie
1999-02-10 17:02 Manfred Spraul
1999-02-11 11:12 ` Stephen C. Tweedie

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=199902081122.LAA02263@dax.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=daniel@msc.cornell.edu \
    --cc=linux-mm@kvack.org \
    /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