From: John Williams <jwilliams@itee•uq.edu.au>
To: khollan <khollan@daktronics•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: SMP on linux with Microblaze?
Date: Tue, 04 Dec 2007 07:18:32 +1000 [thread overview]
Message-ID: <475472A8.1020708@itee.uq.edu.au> (raw)
In-Reply-To: <14137760.post@talk.nabble.com>
Hi,
khollan wrote:
>Now that Full Linux can run on Microblaze with the addition of the MMU, are
>there plans to enable Symmetric Multi-Processing of two or more Microblaze
>cores running Linux?
>
>
This isn't really the right list for direct microblaze discussion, but
since you asked.. The challenge with SMP is not an MMU, but cache
coherency. This is why native SMP on dual PPC on V4/V5 is also a
non-starter. It is possible to build software driven snoop/invalidate
mechanisms that might allow a crippled SMP on MicroBlaze, but I think
the performance would be pretty nasty.
The Blackfin Linux team have done some interesting things towards SMP on
non cache-coherent dual CPUs. Basically they do a local cache
invalidation upon acquiring any kernel lock, on the theory that if you
are accessing a shared data structure you will grab a lock first. Thus,
the cache flush will make sure you get the "true" value, not some stale
locally cached result. But, it's still pretty inefficient, and cannot
do things like processor affinity and process migration. Google the
bfin lists for details and patches.
Regards,
John
prev parent reply other threads:[~2007-12-03 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 20:06 SMP on linux with Microblaze? khollan
2007-12-03 21:18 ` John Williams [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=475472A8.1020708@itee.uq.edu.au \
--to=jwilliams@itee$(echo .)uq.edu.au \
--cc=khollan@daktronics$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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