Le samedi 29 juillet 2006 à 14:23 +0200, Simon Josefsson a écrit : > Eric Leblond <[EMAIL PROTECTED]> writes: > > >> I haven't tried it, but I think it should work. > > > > No sadly, it seems there's a lot in gcrypt and all gets serialized. > > Ouch. Which lock is this?
We do not had the time to point it but on our our quadri processors test platform (thanks to our partner for giving acces to it ;-)) with a thread per gnutls_handshake we clearly manage to see that handshakes finish at regular interval. This indicates that there is now use of multithreading at all. Thus there is a lock. > I agree that locks in libgcrypt are bad, > we should try to remove them, or provide a way to replace libgcrypt > with thread-safer and lock-free alternatives (of which there are > several). Yes it is clearly on important point. > > /Simon _______________________________________________ Help-gnutls mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-gnutls
