From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Craig Arsenault <penguin@wombat.ca>
Cc: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
Tom Rini <trini@kernel.crashing.org>,
<linux-kernel@vger.kernel.org>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: consequences of lowering "MAX_LOW_MEM"?
Date: Wed, 4 Sep 2002 22:02:27 +0200 [thread overview]
Message-ID: <20020904200227.30104@192.168.4.1> (raw)
In-Reply-To: <Pine.LNX.4.44L.0209041453060.8359-100000@tabmow.ca.nortel.com>
>
>> >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 ?
>>
>> Yes, same problem on PPC, you'll run out of virtual space quite
>> quickly for vmalloc and ioremap. Stuff a video board with lots
>> of VRAM or any PCI card exposing large MMIO regions into your
>> machines and it will probably not even boot.
>>
>> Ben.
>>
>
>Ben,
> But doesn't using Matt's suggestion and moving both MAX_LOW_MEM and
>changing KERNELBASE take care of this? It's an embedded board with no
>video, but it does have one PCI Mezzanine Card (PMC) on it.
Yes, Matt's suggestion would work, though I never tried lowering
KERNELBASE. I don't think the kernel supports lowering it below
0x80000000 btw.
Ben.
next prev parent reply other threads:[~2002-09-04 19:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 13:12 consequences of lowering "MAX_LOW_MEM"? Craig Arsenault
2002-09-04 14:26 ` Tom Rini
2002-09-04 15:32 ` Martin J. Bligh
2002-09-03 20:28 ` Benjamin Herrenschmidt
2002-09-04 19:02 ` Craig Arsenault
2002-09-04 20:02 ` Benjamin Herrenschmidt [this message]
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=20020904200227.30104@192.168.4.1 \
--to=benh@kernel.crashing.org \
--cc=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