From: Mark Pilon <mpilon@midrivers.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: KERNELBASE & large memory systems
Date: Mon, 21 Jan 2002 08:07:34 -0700 [thread overview]
Message-ID: <3C4C2EB6.6F3ACADE@midrivers.com> (raw)
In-Reply-To: 3C4A96D7.9010501@embeddededge.com
I've heard that one shouldn't modify the definition of KERNELBASE
as it screws up the MM code;
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.
0xc0000000 - 0xFFFFFFFF is 1Gb; has anyone redefined KERNELBASE
lower to allow for more memory in a system?
Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-21 15:07 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 ` Mark Pilon [this message]
2002-01-21 19:30 ` KERNELBASE & large memory systems Matt Porter
2002-01-21 20:38 ` Dan Malek
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=3C4C2EB6.6F3ACADE@midrivers.com \
--to=mpilon@midrivers.com \
--cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.