Subj : Re: What is the real costs of LOCK on x86 multiprocesor machine?
To   : comp.programming.threads
From : Sean Kelly
Date : Sat Jul 30 2005 10:05 am

Joe Seigh wrote:
>
> Statically or dynamically linked code?  The only case I
> think you can safely get away with making LOCK optional
> is in system dynamically linked libraries that are hardware
> configuration specific.  I use LOCK in inlined code since it's
> in effect statically linked and you don't know where the code
> will eventually execute.

What about testing the hardware configuration on startup and setting a
global state flag?  Would it be worthwhile to do this and deal with the
duplicated asm and branching it would require?


Sean

.