public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Robert Love <rml@tech9.net>
Cc: Clifford White <ctwhite@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: x86 question: Can a process have > 3GB memory?
Date: Wed, 8 May 2002 10:29:34 +0200	[thread overview]
Message-ID: <20020508102934.Z31998@dualathlon.random> (raw)
In-Reply-To: <OF4EFD903E.F8196584-ON87256BB2.007DEC69@boulder.ibm.com> <1020812936.2079.31.camel@bigsur>

On Tue, May 07, 2002 at 04:08:55PM -0700, Robert Love wrote:
> On Tue, 2002-05-07 at 16:03, Clifford White wrote:
> 
> > We are working with a database that requires a large amount of memory
> > allocated by a single process.
> > This is on an Intel 32-bit platform.
> > We'd like to go > 3GB of memory per process.
> > Is this possible on a 32-bit machine? I have been reading the various
> > 'highmem' discussions, but that's kernel page tables...
> > Or is this a glibc issue, and not proper for a kernel-list question?
> > Any pointers would be appreciated. The Intel ESMA (Extended Server Memory
> > Arch) page states that it's possible, but.....how?
> 
> You can go to 3.5GB, anything more and stuff starts getting real tight
> and not very nice.  You can only do 3.5/0.5 on non-PAE, though - PAE
> requires segments to be aligned on 1GB-boundaries.
> 
> The attached patch (for which credit goes elsewhere - Ingo or Randy, I
> think?) implements the full range of 1 to 3.5GB user space partitioning,

actually I'm the one who wrote the 3.5G config option both in 2.2 and
recently I forward ported it to 2.4 due the number of requests I was
getting.

> selectable at compile-time.
> 
> 	Robert Love
> 




Andrea

  parent reply	other threads:[~2002-05-08  8:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07 23:03 x86 question: Can a process have > 3GB memory? Clifford White
2002-05-07 23:08 ` Robert Love
2002-05-08  5:33   ` Martin J. Bligh
2002-05-08  8:29   ` Andrea Arcangeli [this message]
2002-05-08 16:21     ` Robert Love
2002-05-07 23:33 ` Alan Cox
2002-05-08 16:54   ` Bill Davidsen
2002-05-08  0:16 ` Gerrit Huizenga
2002-05-08  0:56   ` Rik van Riel
2002-05-08 15:12     ` Martin J. Bligh
2002-05-08 15:17       ` Rik van Riel
2002-05-08 15:24       ` Andi Kleen
2002-05-09 21:24     ` tchiwam
2002-05-09 21:40       ` Robert Love
2002-05-09 23:56         ` Albert D. Cahalan
2002-05-10  6:58           ` Anton Blanchard
2002-05-10 19:07         ` Bill Davidsen
2002-05-10 19:42           ` Alan Cox
2002-05-10 19:41             ` Linus Torvalds
2002-05-08  8:22 ` Luigi Genoni

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=20020508102934.Z31998@dualathlon.random \
    --to=andrea@suse.de \
    --cc=ctwhite@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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