> > It should in principle be SMP safe.
>
> I don't think so.
You are quite right. It was an offhand remark
that should have been better qualified. The basic
mechanism requires no global memory resource
and will detect discontinuitues in scheduling on
several CPUs at once, but but it is certainly not
SMP safe in the sense of the code sample
providing atomic increment on a classical SMP
hardware platform.
Regards,
Kevin K.
