From: Jens Axboe <axboe@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: 2G memory split
Date: Tue, 10 Jan 2006 14:37:29 +0100 [thread overview]
Message-ID: <20060110133728.GB3389@suse.de> (raw)
In-Reply-To: <20060110132957.GA28666@elte.hu>
On Tue, Jan 10 2006, Ingo Molnar wrote:
>
> * Jens Axboe <axboe@suse.de> wrote:
>
> > Hi,
> >
> > It does annoy me that any 1G i386 machine will end up with 1/8th of
> > the memory as highmem. A patch like this one has been used in various
> > places since the early 2.4 days at least, is there a reason why it
> > isn't merged yet? Note I just hacked this one up, but similar patches
> > abound I'm sure. Bugs are mine.
>
> yes, i made it totally configurable in 2.4 days: 1:3, 2/2 and 3:1 splits
> were possible. It was a larger patch to enable all this across x86, but
> the Kconfig portion was removed a bit later because people _frequently_
> misconfigured their kernels and then complained about the results.
How is this different than all other sorts of misconfigurations? As far
as I can tell, the biggest "problem" for some is if they depend on some
binary module that will of course break with a different page offset.
For simplicity, I didn't add more than the 2/2 split, where we could add
even a 3/1 kernel/user or a 0.5/3.5 (I think sles8 had this).
> so for now the trivial solution is to change the "C" to "8" in the
> following line in include/asm-i386/page.h:
>
> > #define __PAGE_OFFSET (0xC0000000)
>
> instead of editing your .config :-)
:-)
That is what I have been doing, but that requires me to carry this patch
along with me all the time. So it annoys me!
I would have posted a simple patch moving it to 0xB0000000 which would
solve the problem for me as well, but I didn't because I'm sure people
would be screaming at me...
> Maybe we could try the Kconfig solution again, but it'll need alot
> better documentation, dependency on KERNEL_DEBUG and some heavy warnings
> all around.
The help text could definitely be improved, it was a 30 second hackup.
Why would you want to make it depend on DEBUG?
--
Jens Axboe
next prev parent reply other threads:[~2006-01-10 13:35 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 12:58 2G memory split Jens Axboe
2006-01-10 13:29 ` Ingo Molnar
2006-01-10 13:37 ` Jens Axboe [this message]
2006-01-10 13:43 ` Byron Stanoszek
2006-01-10 13:47 ` Jens Axboe
2006-01-10 14:39 ` Jens Axboe
2006-01-10 14:44 ` Ingo Molnar
2006-01-10 15:03 ` [PATCH] Address space split configuration Jens Axboe
2006-01-10 15:11 ` Mark Lord
2006-01-10 15:24 ` Mikael Pettersson
2006-01-10 16:14 ` 2G memory split Linus Torvalds
2006-01-10 16:40 ` Mark Lord
2006-01-10 16:52 ` Linus Torvalds
2006-01-10 18:33 ` Coywolf Qi Hunt
2006-01-10 17:07 ` Mark Lord
2006-01-10 17:28 ` Linus Torvalds
2006-01-10 17:32 ` Jens Axboe
2006-01-10 17:37 ` Mark Lord
2006-01-10 18:58 ` Mark Lord
2006-01-10 19:16 ` [PATCH ] VMSPLIT config options (with default config fixed) Mark Lord
2006-01-10 17:37 ` Jeff V. Merkey
2006-01-10 19:27 ` Jens Axboe
2006-01-11 1:13 ` J.A. Magallon
2006-01-11 10:15 ` Jens Axboe
2006-01-11 16:00 ` Greg Norris
2006-01-11 17:13 ` Mark Lord
2006-01-11 17:44 ` Greg Norris
2006-02-05 18:42 ` Barry K. Nathan
2006-02-01 22:23 ` Herbert Poetzl
2006-02-02 11:04 ` Ulrich Mueller
2006-02-02 20:55 ` Jan Engelhardt
2006-02-03 22:39 ` Mark Lord
2006-02-04 10:23 ` Ulrich Mueller
2006-02-04 11:06 ` Jan Engelhardt
2006-02-04 10:36 ` Jens Axboe
2006-02-04 11:05 ` Jan Engelhardt
2006-02-04 13:57 ` Mark Lord
2006-02-05 15:32 ` J.A. Magallon
2006-02-05 15:38 ` Arjan van de Ven
2006-02-05 21:14 ` Jan Engelhardt
2006-02-05 21:19 ` Arjan van de Ven
2006-02-06 14:56 ` Jan Engelhardt
2006-02-07 0:41 ` Herbert Poetzl
2006-02-07 2:51 ` Mark Rustad
2006-02-07 9:38 ` Bernd Petrovitsch
2006-02-07 12:19 ` RFC: add an ADVANCED_USER option Adrian Bunk
2006-02-07 14:05 ` Ulrich Mueller
2006-02-07 14:42 ` Adrian Bunk
2006-02-09 16:06 ` Jan Engelhardt
2006-01-10 17:48 ` 2G memory split Bernd Eckenfels
2006-01-10 16:30 ` [PATCH] " Jeff V. Merkey
2006-01-10 18:50 ` Lennart Sorensen
2006-01-10 17:13 ` Jeff V. Merkey
2006-01-10 19:42 ` Jens Axboe
2006-01-10 20:17 ` Bernd Eckenfels
2006-01-10 20:28 ` Jens Axboe
2006-01-11 8:39 ` Bernd Eckenfels
2006-01-11 10:06 ` Jens Axboe
2006-01-10 18:14 ` Martin Bligh
2006-01-10 18:34 ` Linus Torvalds
2006-01-10 16:56 ` Jeff V. Merkey
2006-01-10 17:01 ` Jeff V. Merkey
2006-01-10 18:45 ` Mark Lord
2006-01-10 18:46 ` Martin Bligh
2006-01-10 18:58 ` Jens Axboe
2006-01-10 17:17 ` Jeff V. Merkey
2006-01-10 20:55 ` Alan Cox
2006-01-10 19:12 ` Jeff V. Merkey
2006-01-10 21:02 ` Jens Axboe
2006-01-10 19:30 ` Jeff V. Merkey
2006-01-10 18:39 ` Martin Bligh
2006-01-10 18:55 ` Dave Hansen
2006-01-10 19:01 ` Mark Lord
2006-01-10 19:05 ` Dave Hansen
2006-01-10 17:07 ` Sergey Vlasov
2006-04-10 14:11 ` Kirill Korotaev
2006-04-10 14:39 ` Mark Lord
2006-01-10 18:28 ` Coywolf Qi Hunt
2006-01-10 13:47 ` Mikael Pettersson
2006-01-10 13:54 ` Jens Axboe
2006-01-10 14:09 ` Gerd Hoffmann
2006-01-10 14:21 ` Jens Axboe
2006-01-10 14:25 ` Jens Axboe
2006-01-10 20:42 ` Jan Engelhardt
2006-01-11 0:25 ` Con Kolivas
2006-01-10 14:12 ` Mark Lord
2006-01-10 14:22 ` Jens Axboe
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=20060110133728.GB3389@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).