Subject: Re: CVS commit: src/sys/arch/sparc/sparc
To: Brett Lymn <blymn@baesystems.com.au>
From: Jason Thorpe <thorpej@wasabisystems.com>
List: port-sparc
Date: 04/15/2004 19:05:42
--Apple-Mail-42-694727216
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII; format=flowed


On Apr 15, 2004, at 7:01 PM, Brett Lymn wrote:

> cache flushing would probably be the least of your worries given that
> the HyperSPARC processors do some serious snooping of each other's
> caches so there would be some serious cache coherency problems.  That
> totally leaves aside the variations in write posting behaviour :)

But do they use the same snooping protocol as SuperSPARCs?  What about 
I-cache handling?

The point is, there are differences between the two types, and trying 
to handle those on a per-cpu basis is not practical.

         -- Jason R. Thorpe <thorpej@wasabisystems.com>


--Apple-Mail-42-694727216
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQFAfz9+OpVKkaBm8XkRAoaZAKCWC3n+hYY9ngFitbF0AgeFsmyIfwCgtjTF
6idnw+qL6RDrrI3SIRa4aX0=
=OASu
-----END PGP SIGNATURE-----

--Apple-Mail-42-694727216--