From: Dave Hansen <haveblue@us.ibm.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: more than 3 GB in userspace (4G/4G patch?) for 2.6.16
Date: Tue, 13 Jun 2006 14:37:01 -0700 [thread overview]
Message-ID: <1150234621.20249.4.camel@localhost.localdomain> (raw)
In-Reply-To: <e6napj$3j0$1@terminus.zytor.com>
On Tue, 2006-06-13 at 14:30 -0700, H. Peter Anvin wrote:
> > A 0.5/3.5 GB split appears to be what I need for my application.
>
> That is incompatible with PAE. The way PAE works, the split has to be
> an even number of gigabytes.
Well, there have been ancient patches available in the past. People pop
up now and again and ask for them. This is _horribly_ out of date, but
it at least indicates that this is possible.
The basic idea is that you never share a kernel PMD page. Each process
needs to allocate four of its own:
http://lkml.org/lkml/2003/5/9/138
-- Dave
prev parent reply other threads:[~2006-06-13 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 20:30 more than 3 GB in userspace (4G/4G patch?) for 2.6.16 Hanno Mueller
2006-06-13 21:30 ` H. Peter Anvin
2006-06-13 21:37 ` Dave Hansen [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=1150234621.20249.4.camel@localhost.localdomain \
--to=haveblue@us.ibm.com \
--cc=hpa@zytor.com \
--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