From: Dave Hansen <haveblue@us.ibm.com>
To: Chuck Luciano <chuck@mrluciano.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: redhat 2.4.20 kernel 3.5G patch, bug report on my previous 2.4.18 kernel 3.5G patch
Date: 19 Aug 2003 14:16:58 -0700 [thread overview]
Message-ID: <1061327818.25944.48.camel@nighthawk> (raw)
In-Reply-To: <NFBBKNADOLMJPCENHEALCENAGLAA.chuck@mrluciano.com>
On Tue, 2003-08-19 at 10:55, Chuck Luciano wrote:
> Again, I've been kinda lazy about adding the configuration stuff,
> but, this patch applied to kernel-2.4.20-18.7.src.rpm will give
> you a kernel where PAGE_OFFSET can be set with 2 MB granularity
> instead of 1GB.
This sounds familar from somewhere. A little attribution to the source
of the code would be nice. :)
> BTW, there is a defect in the 2.4.18 version of this patch in the
> function get_pgd_slow which doesn't handle the partial PGD
> properly. In 2.4.20 the fix for this problem is in the function
> pgd_alloc. I will probably not have time to back port this fix to
> 2.4.18.
Actually, I would just do what we did in 2.5 and throw away *_pgd_fast()
functions and just use a slab constructor and destructor to handle it
for you.
> Anyway, for your fun and amusement, the 2.4.20 patch is working
> and ready for use. I haven't tried seeing just how far I can push
> PAGE_OFFSET yet, but I'd like to see how close I can get to
> 0xf0000000 and maybe beyond.
I know I've done at least 0xf8000000 on 2.5.
--
Dave Hansen
haveblue@us.ibm.com
next prev parent reply other threads:[~2003-08-19 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 17:55 redhat 2.4.20 kernel 3.5G patch, bug report on my previous 2.4.18 kernel 3.5G patch Chuck Luciano
2003-08-19 21:16 ` Dave Hansen [this message]
2003-08-19 21:39 ` William Lee Irwin III
2003-08-19 22:51 ` redhat 2.4.20 kernel 3.5G patch, bug report on my previous2.4.18 " Chuck Luciano
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=1061327818.25944.48.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=chuck@mrluciano.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 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.