Paul Rubin schrieb: > "Martin v. Löwis" <[EMAIL PROTECTED]> writes: >>> PS: Besides: what are speed costs of LOCK INC <mem> ? >> That very much depends on the implementation. In >> http://gcc.gnu.org/ml/java/2001-03/msg00132.html >> Hans Boehm claims it's 15 cycles. > > I think that has to be on a single processor, or at most a dual core > processor with shared cache on die. With multiple cpu chips I don't > think can get the signals around that fast.
Can you explain what you mean? The lock# signal takes *immediate* effect, within the CPU cycle in which it is asserted. There is no delay whatsoever (except for speed-of-light issues, of course). Regards, Martin -- http://mail.python.org/mailman/listinfo/python-list
