From: Ralf Baechle <ralf@linux-mips.org>
To: David VomLehn <dvomlehn@cisco.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Does HIGHMEM work on 32-bit MIPS ports?
Date: Wed, 20 Feb 2008 16:18:44 +0000 [thread overview]
Message-ID: <20080220161844.GC25644@linux-mips.org> (raw)
In-Reply-To: <47BBA809.3050505@cisco.com>
On Tue, Feb 19, 2008 at 08:09:45PM -0800, David VomLehn wrote:
> As we continue to investigate using high memory on MIPS, we keep coming up
> with odd results. The basic mapping of high memory seems to be working
> correctly, and if we use an INITRAMFS root filesystem, things seem to work.
> Things also seem to work with an NFS root filesystem if we disable
> preemption, though we get someone squirrelly behavior in some minor ways.
> Has anyone else successfully been able to use high memory on a 32-bit MIPS
> Linux port?
I've written MIPS highmem support in late 2002 for a customer who back
then wasn't interested in being the first through the 64-bit minefield.
Which back then certainly was justified - but there are now fairly
stable 64-bit Linux kernels available so if you happen to be running on
64-bit hardware don't even spend a nanosecond on thinking about 32-bit
highmem kernels. Highmem fundamentally sucks rocks through a straw.
Coming back to your question. Highmem was only ever tested to work on
SB1 and somewhat later PMC-Sierra RM9000 cores, both being 64-bit. With
the increasing maturity of 64-bit Linux interest in these went away and
as the result the highmem code started a slow bitrot - unnoticed for many
moons.
Ralf
next prev parent reply other threads:[~2008-02-20 16:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 4:09 Does HIGHMEM work on 32-bit MIPS ports? David VomLehn
2008-02-20 16:18 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-20 19:20 David VomLehn
2008-02-21 10:55 ` Maciej W. Rozycki
2008-02-26 21:06 David VomLehn
2008-03-05 22:55 David VomLehn
2008-03-06 15:44 ` Ralf Baechle
2008-03-07 5:02 David VomLehn
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=20080220161844.GC25644@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=dvomlehn@cisco.com \
--cc=linux-mips@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