From: Ralf Baechle <ralf@linux-mips.org>
To: Nilanjan Roychowdhury <Nilanjan.Roychowdhury@gnss.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Inter processor synchronization
Date: Thu, 13 Dec 2007 12:58:47 +0000 [thread overview]
Message-ID: <20071213125847.GA1352@linux-mips.org> (raw)
In-Reply-To: <9D98C51005D80D43A19A3DF329A61D690106A282@INDEXCH2003.gmi.domain>
On Thu, Dec 13, 2007 at 09:07:20AM +0530, Nilanjan Roychowdhury wrote:
> I have a scenario where two images of the same Linux kernel are running
> on two MIPS cores. One is 24K and another is 4KEC. What is the best way
> to achieve inter processor synchronization between them?
>
> I guess the locks for LL/SC are local to a particular core and can not
> be extended across a multi core system.
4K and 24K cores don't support cache coherency. So SMP is out of question.
This is a _total_ showstopper for SMP, don't waste your time thinking on
possible workarounds.
The you could do is some sort of clusting, running two OS images, one
on the 4K and one on the 24K which would communicate through a carefully
cache managed or even uncached shared memory region.
> Will it be easier for me if both of them becomes same core ( like both
> 24k) and I run the SMP version of Linux.
Within limits Linux supports mixing different CPU types such as R4000MC /
R4400MC and R10000 / R12000 / R14000 mixes because those processors are
similar enough
Ralf
next prev parent reply other threads:[~2007-12-13 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 3:37 Inter processor synchronization Nilanjan Roychowdhury
2007-12-13 3:37 ` Nilanjan Roychowdhury
2007-12-13 12:58 ` Ralf Baechle [this message]
2007-12-14 4:21 ` Nilanjan Roychowdhury
2007-12-14 4:21 ` Nilanjan Roychowdhury
2007-12-14 9:26 ` Kevin D. Kissell
2007-12-14 9:26 ` Kevin D. Kissell
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=20071213125847.GA1352@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Nilanjan.Roychowdhury@gnss.com \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.