All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Maximum Physical Memory on 2.4 and ia32
Date: Sun, 1 Dec 2002 23:04:12 -0800	[thread overview]
Message-ID: <20021202070412.GO697@holomorphy.com> (raw)
In-Reply-To: <20021202120835.4ecb87fd.sfr@canb.auug.org.au>

On Mon, Dec 02, 2002 at 12:08:35PM +1100, Stephen Rothwell wrote:
> (http://www.redhat.com/services/techsupport/production/GSS_caveat.html)
> What are the "operating system design limits" that restrict the amount of
> supported memory to 16GB?

I've relayed this privately in less organized private discussions:

The design limitation is that a PTE is required to map a PAGE_SIZE
-sized region. The kernel allocation unit needs to be enlarged without
breaking ABI to reduce the fraction of physical memory reserved for
metadata i.e. mem_map[]. This is called page clustering.

Hugh Dickins implemented page clustering by creating a distinction
between PAGE_SIZE and MMUPAGE_SIZE then introducing an API for dealing
with vectors of PTE's. He implemented this for 2.4.6 and 2.4.7. His
patches are at ftp://ftp.veritas.com/linux/ In other environments this
is an optimization, not a requirement to be able to run, and so it
benefits all platforms.

There are, of course, other kinds of metadata generated at runtime that
may impose limitations on feasibility of workloads on large highmem boxen.

Bill

      parent reply	other threads:[~2002-12-02  6:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02  1:08 Maximum Physical Memory on 2.4 and ia32 Stephen Rothwell
2002-12-02  2:44 ` Andrew Morton
2002-12-02  6:48   ` Martin J. Bligh
2002-12-02  7:04 ` William Lee Irwin III [this message]

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=20021202070412.GO697@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.