Faster mutex lock() and unlock()

Victor Stinner haypo at
Thu Jul 13 10:32:57 CEST 2006


> haypo at wrote:
>> I would like to know your opinion about replacing old ath_mutex_lock()
> I don't think so
> (...)
> Yes, there is a small overhead.  The overhead is a lock instruction.
That's significant, but ath was not written for performance, but for
> (...)

Ok, I understand. I don't want to break libgcrypt API/behaviour. I just
try to understand where my program is spending a lot of time, and I have
difficulties to read gprof results ...

Victor Stinner aka haypo

More information about the Gcrypt-devel mailing list