From: Scott Wood <scottwood@freescale.com>
To: vijay baskar <cn.vijaibaskar@gdatech.co.in>
Cc: 郭劲 <guojin02@tsinghua.org.cn>, linuxppc-embedded@ozlabs.org
Subject: Re: The question about the high memory support on MPC8360?
Date: Tue, 27 Nov 2007 11:02:33 -0600 [thread overview]
Message-ID: <474C4DA9.6000205@freescale.com> (raw)
In-Reply-To: <474B9CC0.2000803@gdatech.co.in>
vijay baskar wrote:
> The kernel maps the last 1 GB of the virtual address space one to one
> to the physical memory.
No, it maps 768MB of RAM in this manner.
> This is called the kernel space. After the one
> to one mapping is done for the available physical memory, the
> remaining virtual addresses are used for vmalloc and ioremap.
And highmem mappings.
> The kernel also allows hardcoded mapping
> of IO regions into its virtual address space through the
> io_block_mapping interface.
Not in current arch/powerpc kernels.
> Many boards use the block IO mapping to
> map the CCSRBAR/IMMR into the kernel address space, such that the
> physical address and the virutal address is the same. Virtual
> addresses beyond these hardcoded mappings cannot be used by
> vmalloc/ioremap.
And this is why.
> Now as more and more memory is added to the system the addresses
> available for vmalloc and ioremap gets reduced, and memory allocations
> start to fail, due to the lack of availability of virtual addresses.
How so? The size of lowmem is constant once you reach the threshold, as
is the size of the highmem mapping area.
What *does* start to fail eventually, if you have a *lot* of highmem, is
that you run out of lowmem for pagetables and such.
-Scott
next prev parent reply other threads:[~2007-11-27 17:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 3:58 The question about the high memory support on MPC8360? 郭劲
2007-11-26 6:11 ` vijay baskar
2007-11-26 16:57 ` Scott Wood
2007-11-27 4:27 ` vijay baskar
2007-11-27 17:02 ` Scott Wood [this message]
2007-11-28 4:02 ` vijay baskar
2007-11-28 16:57 ` Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2007-11-29 3:11 郭劲
2007-11-29 7:29 ` vijay baskar
2007-11-29 12:59 ` robert lazarski
2007-11-29 16:09 ` Dale Farnsworth
2007-11-29 19:41 ` Rune Torgersen
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=474C4DA9.6000205@freescale.com \
--to=scottwood@freescale.com \
--cc=cn.vijaibaskar@gdatech.co.in \
--cc=guojin02@tsinghua.org.cn \
--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).