From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Max mem space per process under 2.6.13-15.7-smp
Date: Tue, 28 Feb 2006 19:09:33 -0600 [thread overview]
Message-ID: <4404F44D.1080600@shaw.ca> (raw)
In-Reply-To: <5LmVi-6om-11@gated-at.bofh.it>
Kai Lampka wrote:
> Sorry to bother,
> but what is the maximum amount of RAM that a *single* (!) process can
> address under a Kernel version 2.6.13-15.7-smp, with
>
> CONFIG_HIGHMEM64G=y
> CONFIG_HIGHMEM=y
> CONFIG_X86_PAE=y
>
> It seems that I can not get over 3 Gig border, but i need to, to solve
> my numerical problems :(.
If you use a kernel with the 4G-4G user-kernel space split patch, you
can get a full 4GB. To get more than that you will need to move to 64-bit.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-03-01 1:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5LmVi-6om-11@gated-at.bofh.it>
2006-03-01 1:09 ` Robert Hancock [this message]
2006-02-28 23:55 Max mem space per process under 2.6.13-15.7-smp Kai Lampka
2006-03-01 0:11 ` Douglas McNaught
2006-03-01 7:25 ` Arjan van de Ven
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=4404F44D.1080600@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.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