From: "Krishna Chaitanya" <lnxctnya@gmail.com>
To: "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux for Asymmetric Multi Processing Systems.
Date: Sat, 13 May 2006 17:40:54 +0530 [thread overview]
Message-ID: <ae649ba00605130510p6435e756h86f310f814c14b66@mail.gmail.com> (raw)
In-Reply-To: <20060512185426.GC2837@csclub.uwaterloo.ca>
Hi Len,
Each Processor has its own RAM and the main ARM9 processor can access
the ARM7 Memory Map through a _Shared RAM_.
In other words, the Memory Map of ARM7 processors is visible to ARM9 processor.
Finally there are 3 RAMs:
1) System RAM (ARM9)
2) Shared RAM (the Common Memory)
3) Local RAM for ARM7s.
Basically, this is a _flexible_ mechanism to control the _visibility_
of Each Processor.
And the Memory Controller can do either _cached_ or _non-cached_ operations.
Regards,
krs
On 5/13/06, Lennart Sorensen <lsorense@csclub.uwaterloo.ca> wrote:
> On Fri, May 12, 2006 at 12:24:20PM +0530, Krishna Chaitanya wrote:
> > I am working on a project where the hardware is Asymmetric Multi
> > Processing Systems(ASMP).
> >
> > In my system I have one ARM9, four ARM7s'.
> >
> > 1. Can I use one Linux Kernel for all the CPUs in an ASMP system. (or)
> > Should I use One Linux Kernel for ARM9 and RTOSes for ARM7.
> > 2. If my hardware would come up in future with another ARM7 does linux
> > scale for the new CPU.
> >
> > Can anyone please direct me to the source/docs how to use Linux for
> > ASMP systems.
>
> So you have two different instruction sets (although I think the arm7 is
> a subset of the arm9, but what do I know), running different clocks
> speeds most likely.
>
> Does each cpu have it's own ram, or do they all share one pool of memory?
>
> How does the Cell processor systems deal with this?
>
> Len Sorensen
>
next prev parent reply other threads:[~2006-05-13 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 6:54 Krishna Chaitanya
2006-05-12 18:54 ` Lennart Sorensen
2006-05-13 12:10 ` Krishna Chaitanya [this message]
2006-05-15 13:04 ` Lennart Sorensen
2006-05-15 7:32 ` Zhou Yingchao
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=ae649ba00605130510p6435e756h86f310f814c14b66@mail.gmail.com \
--to=lnxctnya@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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®