| To: | macro@ds2.pg.gda.pl (Maciej W. Rozycki) |
|---|---|
| Subject: | Re: PATCH: Fix ll/sc for mips (take 3) |
| From: | Hartvig Ekner <hartvige@mips.com> |
| Date: | Tue, 5 Feb 2002 20:28:34 +0100 (MET) |
| Cc: | linux-mips@oss.sgi.com |
| In-reply-to: | <Pine.GSO.3.96.1020205134113.9674G-100000@delta.ds2.pg.gda.pl> from "Maciej W. Rozycki" at Feb 05, 2002 02:28:59 PM |
| Sender: | owner-linux-mips@oss.sgi.com |
Maciej W. Rozycki writes: > How do you maintain coherency on such a system? To support such a model > all shared area write accesses should be followed by explicit > synchronization requests. It should be trivial but tedious to do for > Linux, but it might not be that easy for threads. This would have to be a loosely coupled system - something using either software coherency or uncached accesses for the shared areas. And then LL/SC for synchronization primitives. There are a fair number of SOC designs like this, even with more than two processors. /Hartvig |
| Previous by Date: | Re: What is the maximum physical RAM for a 32bit MIPS core?, Hartvig Ekner |
|---|---|
| Next by Date: | Re: PATCH: Fix ll/sc for mips (take 3), H . J . Lu |
| Previous by Thread: | Re: PATCH: Fix ll/sc for mips (take 3), Maciej W. Rozycki |
| Next by Thread: | Re: PATCH: Fix ll/sc for mips (take 3), Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |