From: Giuliano Pochini <pochini@shiny.it>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@lists.linuxppc.org, Amit Shah <amitshah@gmx.net>,
Dan Malek <dan@embeddededge.com>
Subject: Re: IBM 750GX SMP on Marvell Discovery II or III?
Date: Wed, 12 May 2004 09:57:56 +0200 (CEST) [thread overview]
Message-ID: <XFMail.20040512095756.pochini@shiny.it> (raw)
In-Reply-To: <16545.27647.651552.393992@cargo.ozlabs.ibm.com>
On 12-May-2004 Paul Mackerras wrote:
>
> The only workaround I can see for this is to completely flush the D
> and I caches of both CPUs whenever we schedule a process on a
> different CPU from that on which it last ran. Triple yuck.
It's not very different than what Linux does with NUMA
systems AFAIK. If some cache management instructions cause
troubles and it is an embedded system, it may be a good
solution recompiling user space stuff removing problematic
parts.
--
Giuliano.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-12 7:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 7:28 IBM 750GX SMP on Marvell Discovery II or III? Amit Shah
2004-05-10 23:36 ` Paul Mackerras
2004-05-11 2:09 ` Dan Malek
2004-05-11 3:03 ` Paul Mackerras
2004-05-11 15:46 ` Dan Malek
2004-05-11 17:23 ` Huailin Chen
2004-05-11 17:31 ` Amit Shah
2004-05-11 20:51 ` Huailin Chen
2004-05-12 0:17 ` Paul Mackerras
2004-05-12 0:12 ` Paul Mackerras
2004-05-12 7:57 ` Giuliano Pochini [this message]
2004-05-12 8:00 ` Gabriel Paubert
2004-05-12 10:26 ` Benjamin Herrenschmidt
2004-05-12 11:53 ` Gabriel Paubert
2004-05-12 11:46 ` Paul Mackerras
2004-05-12 13:45 ` Gabriel Paubert
2004-05-12 14:21 ` Geert Uytterhoeven
2004-05-12 14:30 ` Amit Shah
2004-05-13 4:30 ` Bryan Rittmeyer
2004-05-14 8:02 ` Geert Uytterhoeven
2004-05-14 9:11 ` Gabriel Paubert
2004-05-11 3:08 ` Huailin Chen
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=XFMail.20040512095756.pochini@shiny.it \
--to=pochini@shiny.it \
--cc=amitshah@gmx.net \
--cc=dan@embeddededge.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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).