From: Roland Dreier <roland@topspin.com>
To: jmerkey@comcast.net
Cc: linux-kernel@vger.kernel.org, jmerkey@drdos.com
Subject: Re: 1GB/2GB/3GB User Space Splitting Patch 2.6.8.1 (PSEUDO SPAM)
Date: Wed, 25 Aug 2004 21:42:28 -0700 [thread overview]
Message-ID: <52n00ibjd7.fsf@topspin.com> (raw)
In-Reply-To: <082620040421.9849.412D655C000690BA000026792200735446970A059D0A0306@comcast.net> (jmerkey@comcast.net's message of "Thu, 26 Aug 2004 04:21:48 +0000")
jmerkey> That incredibly useful patch for 2.4.X that Andrea wrote
jmerkey> that splits the kernel user space into 1GB/2GB/3GB
jmerkey> sections I ported to 2.6.8.1 and posted it to:
jmerkey> ftp.kernel.org:/pub/linux/kernel/people/jmerkey/patches/linux-2.6.8.1-highmem-split-08-25-04.patch
This is indeed pretty useful. A few comments on your version of the patch:
- might as well post a patch this small inline
- In Kconfig, what happens if someone turns on highmem? It seems all
the USER_XXX choices depend on NOHIGHMEM. also, the config option
probably needs at least some help text.
- the change to vmlinux.ld.S can be dropped from future versions
(Linus merged this post-2.6.8)
- why create PAGE_OFFSET_RAW in asm-generic, when it depends on
i386-only config symbols and is only used in i386?
- what's the reason for the odd rewrite of free_one_pgd()? it looks
equivalent (and misindented)
Thanks,
Roland
next prev parent reply other threads:[~2004-08-26 4:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 4:21 1GB/2GB/3GB User Space Splitting Patch 2.6.8.1 (PSEUDO SPAM) jmerkey
2004-08-26 4:33 ` William Lee Irwin III
2004-08-26 4:46 ` Roland Dreier
2004-08-26 4:49 ` William Lee Irwin III
2004-08-26 8:40 ` Ryan Cumming
2004-08-29 12:48 ` Alan Cox
2004-08-29 16:42 ` William Lee Irwin III
2004-08-29 15:45 ` Alan Cox
2004-08-29 17:00 ` William Lee Irwin III
2004-08-26 4:38 ` Martin J. Bligh
2004-08-26 4:42 ` Roland Dreier [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-26 20:24 jmerkey
2004-08-26 20:38 ` William Lee Irwin III
2004-08-26 21:41 ` Dave Jones
2004-08-26 21:08 jmerkey
2004-08-26 21:43 ` William Lee Irwin III
2004-08-26 23:47 linux
2004-08-30 4:01 jmerkey
2004-08-30 4:35 ` Randy.Dunlap
2004-08-30 5:56 jmerkey
2004-08-30 18:10 ` Randy.Dunlap
2004-08-30 18:28 ` Roland Dreier
2004-09-22 18:52 ` Timothy Miller
2004-09-22 18:51 ` Roland Dreier
2004-09-22 20:22 ` Timothy Miller
2004-09-27 14:55 ` Roland Dreier
2004-08-31 22:50 jmerkey
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=52n00ibjd7.fsf@topspin.com \
--to=roland@topspin.com \
--cc=jmerkey@comcast.net \
--cc=jmerkey@drdos.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