mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Tom Rini <trini@kernel.crashing.org>,
	Craig Arsenault <penguin@wombat.ca>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: consequences of lowering "MAX_LOW_MEM"?
Date: Wed, 04 Sep 2002 08:32:15 -0700	[thread overview]
Message-ID: <137715274.1031128333@[10.10.2.3]> (raw)
In-Reply-To: <20020904142636.GL761@opus.bloom.county>

>> In 2.4.x (currently using 2.4.18), for PPC, there is a value for
>> "MAX_LOW_MEM" defined in "arch/ppc/mm/pgtable.c" as 768MB RAM.  Any
>> memory above 768MB is considered "high" memory.  Now our problem is
>> that we have 1024MB of onboard RAM on our card.  I do *NOT* wish to
>> compile with "CONFIG_HIGHMEM" set to true (see below for why), but i
>> do wish to have full use of the 1024MB of RAM onboard, or at least
>> 992MB which is the minimum for our app.
>> So what I did was just change "MAX_LOW_MEM" to be 0x3E000000
>> (0x30000000), ie. change it to 992 from 768.   I recompiled and tested
>> our application.  Things seemed to be running normal with a max of
>> 992MB of RAM.
>> 
>> Is this a potential problem, or will this cause some lurking bug that
>> anyone can think of?  (ie. I'm sure "MAX_LOW_MEM" was set to 768MB for
>> a reason, but what is that reason).   We don't want to move higher
>> than 1Gig RAM for now, so are we going to be okay doing what I
>> describe above?  Any suggestions or comments as to why that's a very
>> bad idea would be greatly appreciated.  Again, this is for a
>> PPC-specific board, I'm not sure what the x86 architecture's low
>> memory max is.

I think you'll find yourself with no virtual address space left to 
do vmalloc / fixmap / kmap type stuff. Or at least you would on i386, 
I presume it's the same for ppc. Sounds like you may have left 
yourself enough space for fixmap & kmap, but any calls to vmalloc
will probably fail ?

M.


  reply	other threads:[~2002-09-04 15:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-04 13:12 Craig Arsenault
2002-09-04 14:26 ` Tom Rini
2002-09-04 15:32   ` Martin J. Bligh [this message]
2002-09-03 20:28     ` Benjamin Herrenschmidt
2002-09-04 19:02       ` Craig Arsenault
2002-09-04 20:02         ` Benjamin Herrenschmidt
2002-09-04 20:56           ` Matt Porter
2002-09-04 16:57     ` Matt Porter
2002-09-04 18:35       ` Craig Arsenault
2002-09-04 19:04         ` Matt Porter

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='137715274.1031128333@[10.10.2.3]' \
    --to=martin.bligh@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=penguin@wombat.ca \
    --cc=trini@kernel.crashing.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

all inboxes | Powered by JetHome®