From: Scott Wood <scottwood@freescale.com>
To: jay_chen <jay_chen@alphanetworks.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Use 2G RAM in 8548, vmalloc fail, adjust_total_lowmem
Date: Wed, 09 Jan 2008 12:59:28 -0600 [thread overview]
Message-ID: <47851990.7020908@freescale.com> (raw)
In-Reply-To: <OF590B6FCB.576A8335-ON482573CB.00169CC3@alphanetworks.com>
jay_chen wrote:
> Hello, all~~~
>
> I am using a MCP8548 board with 2.6.14.5 kernel.
> And I would like to upgrade memory from 512MB to 2048MB.
> Finally, I realize this is not so easy as I think. I encounter several
> problems. :~~
Well, it should be easy if you use highmem...
> First, I change mem=512M to mem=2048M.
>
> 1. vmalloc fail problem
Are you saying you have vmalloc failures if you don't do any of the
below, and enable highmem, with 2GB RAM? Could you provide more details?
> So, I change kernel config in "advanced setup"
> Change "Set maximum low memory" from 0x30000000 to 0x80000000.
> Change "Virtual address of kernel base" from 0xC0000000 to 0x60000000.
> Change "Set custom user task size" from 0x80000000 to 0x60000000
>
> Someone said that he could change "Virtual address of kernel base" to
> 0xA0000000 without problem.
> Could I change it to 0x60000000? Any possible problem?
There are always *possible* problems. :-)
In theory it should work, but it's not a very well tread path.
> In adjust_total_lowmem(), fsl_booke_mmu.c
> It always limits the low memory to 768MB. (no matter we set mem=768MB or
> mem=1024MB, or mem=2048MB)
> __max_low_memory = max_low_mem = __cam0 + __cam1 + __cam2; (each TLB could
> map up to 256MB)
>
> My question is could I use more than 3 TLBs here? Such as 8 TLBs to map 2G
> ram?
Yes.
> Or could I use e500v2 new feature, that is 1 TLB could map up to 4G?
Yes.
-Scott
prev parent reply other threads:[~2008-01-09 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 4:06 Use 2G RAM in 8548, vmalloc fail, adjust_total_lowmem jay_chen
2008-01-09 16:06 ` Dale Farnsworth
2008-01-09 18:59 ` Scott Wood [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=47851990.7020908@freescale.com \
--to=scottwood@freescale.com \
--cc=jay_chen@alphanetworks.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).