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: Wed, 28 Nov 2007 10:57:38 -0600 [thread overview]
Message-ID: <474D9E02.5050302@freescale.com> (raw)
In-Reply-To: <474CE85A.1020902@gdatech.co.in>
vijay baskar wrote:
> Hi, "The kernel also allows hardcoded mapping of IO regions into its
> virtual address space through the io_block_mapping interface."
>
> Can u tell me how this is in current arch/powerpc.
Everything is explicitly ioremapped.
> Also does it mean that whatever be the size of the ram > 768 MB there
> is not going to be much improvement in performance in kernel space
> irrespective of invoking CONFIG_HIGHMEM or not?
Well, the kernel can use highmem for cache... I'm not sure what you
mean by "in kernel space".
> Also do you think this low mem be enough if i have lots of kernel
> space processes each invoking lots of kmallocs.
That depends on what you mean by "lots". :-)
You'll have 768MB of lowmem, and kmallocs can only use lowmem.
> Will there be bottle necks?? Also what alternative do we have if low
> mem of 768 MB is not enough??
You'll need to change the user/kernel split, and deal with anything that
breaks in the process.
Or get a 64-bit chip. :-)
-Scott
next prev parent reply other threads:[~2007-11-28 16:58 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
2007-11-28 4:02 ` vijay baskar
2007-11-28 16:57 ` Scott Wood [this message]
-- 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=474D9E02.5050302@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).