From: Dan Malek <dan@embeddededge.com>
To: Mark Pilon <mpilon@midrivers.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: KERNELBASE & large memory systems
Date: Mon, 21 Jan 2002 15:38:38 -0500 [thread overview]
Message-ID: <3C4C7C4E.4020506@embeddededge.com> (raw)
In-Reply-To: 3C4C2EB6.6F3ACADE@midrivers.com
Mark Pilon wrote:
> I've heard that one shouldn't modify the definition of KERNELBASE
> as it screws up the MM code;
That was true until yesterday. Matt Porter checked in some configuration
changes that if you know what you are doing will change the virtual
mapping windows on most processors (not 4xx or 8xx yet). They are
in the linuxppc_2_4_devel kernel.
> I'm wondering how people out there are handling designing systems
> (and getting linux running) on large pools of memory -- like
> 1 - 2 Gb or so.
The only general answer to that question is the solution depends upon
your configuration. A combination of highmem and kernel address base
changes are used. This will also affect drivers if you have some custom
application and you are trying to use a driver that makes assumptions
about the "normal" kernel mapping.
The "know what you are doing" is critical to your success :-).
Good Luck.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-01-21 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-20 10:07 consistent_alloc changes for 4xx/8xx Dan Malek
2002-01-21 15:07 ` KERNELBASE & large memory systems Mark Pilon
2002-01-21 19:30 ` Matt Porter
2002-01-21 20:38 ` Dan Malek [this message]
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=3C4C7C4E.4020506@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mpilon@midrivers.com \
/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).