Exploiting Dual Core's with Py_NewInterpreter's separated GIL ?
"Martin v. Löwis"
martin at v.loewis.de
Sun Nov 5 04:20:29 CET 2006
Paul Rubin schrieb:
> "Martin v. Löwis" <martin at v.loewis.de> writes:
>>> PS: Besides: what are speed costs of LOCK INC <mem> ?
>> That very much depends on the implementation. In
>> 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).
More information about the Python-list