Re: multithreading on a multiprocessor system ( a bit OT )

[Justin Carlson]

--=-71eFP1xpZ+3cUOAXxsuU
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 2002-01-16 at 14:49, R. Sinoradzki wrote:
> O.K my question:
> Consider two modern processors that share some data and a lock.
> The lock may be implemented with something like an atomic test-and-set
> instruction. Now processor 'A' acquires the lock and works with the data.
> Processor 'B' also wants to access the data, but internally reorders it's
> instructions because the instructions seem independent from each other.
> So 'B' might access the data without having the lock.
> If it's a single processor system, reordering instructions in a way that
> ensures that it looks 'as if' everything has been executed in the right o=
rder
> might be easy, but in a multiprocessor system 'A' doesn't know 'B's state=
.

Then you've got a bug.  Modern implementations that do SMP provide some
way of placing barriers around speculative execution structures to make
sure you don't, say, go out and read some memory location that changes
state in a device because that's an OK speculative action to take.

Can't really comment on x86, as I'm not very good with it, but taking
for example MIPS and Alpha, in addition to the ll-sc ops, there are a
sync and mb instructions, respectively, which provide a method for
assuring that previous operations have become visible in terms of
general machine state before going on.

-Justin

--=-71eFP1xpZ+3cUOAXxsuU
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQA8Rd+s47Lg4cGgb74RAnxeAJ42+wPvabJmfNf4wOHD/fPNra8XRgCcD4TC
cRNyj0fjHwjkUn23Vkl1fQQ=
=BWIY
-----END PGP SIGNATURE-----

--=-71eFP1xpZ+3cUOAXxsuU--