From: Jon Anders Haugum <jonah@omegav.ntnu.no>
To: ralf@linux-mips.org
Cc: linux-mips@linux-mips.org
Subject: Re: HIGHMEM
Date: Tue, 7 Dec 2004 11:29:04 +0100 (CET) [thread overview]
Message-ID: <20041207112038.X44387@invalid.ed.ntnu.no> (raw)
In-Reply-To: <003801c4dc45$f9212690$2203a8c0@qfree.com>
> In 2.4 the support for CONFIG_DISCONTIG and CONFIG_NUMA are a bit tangled
> with each other because IP27 is the only platform to uses these features and
> it needs both. Other than that you can also just setup your system as 0x0 -
> 0x10000000 being RAM, 0x10000000 - 0x20000000 being reserved memory and
> 0x20000000 - 0x30000000 being highmem. Which works but is a bit wasteful.
>
> Issue #2 is that we don't support the combination of CONFIG_DISCONTIG and
> CONFIG_HIGHMEM. And highmem is a lobotomized solution for lobotomized
> silicon anyway. You have a 64-bit processor - use it's capabilities :-)
>
> Issue #3 - As I recall the TX4937's H3 core is suffering from cache aliases.
> Handling those efficiently for highmem is not easily possible and so we
> don't even try. More recent kernels will refuse to enable highmem on such
> cache configurations but something like 2.4.18 which by now is an almost 3
> year old antique doesn't know about that and will happily crash.
>
> I recommend you should go for a 64-bit kernel instead. And 64-bit support
> is certainly better in 2.6 than in 2.4. Especially the area of 32-bit
> binary compatibility has been improved significantly.
What about on a processor like the AMD au1550?
I've tried the latest from 2.4 branch in cvs, and I haven't been
successful in geting past INIT either...
Can I place all the memory from address 0x20000000 to get more than
256Meg?
--
Jon Anders Haugum
next parent reply other threads:[~2004-12-07 10:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <003801c4dc45$f9212690$2203a8c0@qfree.com>
2004-12-07 10:29 ` Jon Anders Haugum [this message]
2004-12-15 14:18 ` HIGHMEM Ralf Baechle
2004-12-07 1:07 HIGHMEM Hdei Nunoe
2004-12-07 1:07 ` HIGHMEM Hdei Nunoe
2004-12-07 9:17 ` HIGHMEM Jan-Benedict Glaw
2004-12-07 9:56 ` HIGHMEM Hdei Nunoe
2004-12-07 9:56 ` HIGHMEM Hdei Nunoe
2004-12-07 10:02 ` HIGHMEM Jan-Benedict Glaw
2004-12-07 9:58 ` HIGHMEM Ralf Baechle
2004-12-13 4:34 ` HIGHMEM Atsushi Nemoto
2004-12-15 14:16 ` HIGHMEM Ralf Baechle
2004-12-21 14:33 ` HIGHMEM Atsushi Nemoto
2004-12-14 4:26 ` HIGHMEM Hdei Nunoe
2004-12-14 4:26 ` HIGHMEM Hdei Nunoe
2004-12-15 14:15 ` HIGHMEM Ralf Baechle
2005-01-11 2:33 ` HIGHMEM Hdei Nunoe
2005-01-11 2:33 ` HIGHMEM Hdei Nunoe
2005-01-11 10:34 ` HIGHMEM Ralf Baechle
2005-01-11 10:38 ` HIGHMEM Geert Uytterhoeven
2005-01-11 13:51 ` HIGHMEM Ralf Baechle
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=20041207112038.X44387@invalid.ed.ntnu.no \
--to=jonah@omegav.ntnu.no \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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