From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id p2Q6lkUm021361 for ; Sat, 26 Mar 2011 07:47:46 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ai4CAAeLjU1KfVI0kGdsb2JhbAClWAgUAQEBAQkJDQcUBCGnbYpUgiGEcS+IXAEBAwWFZASFOIc9iQo6 X-IronPort-AV: E=Sophos;i="4.63,247,1299452400"; d="scan'208";a="103674611" Received: from mail-ww0-f52.google.com ([74.125.82.52]) by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 26 Mar 2011 07:47:41 +0100 Received: by wwe15 with SMTP id 15so1683075wwe.9 for ; Fri, 25 Mar 2011 23:47:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=jyJEVXfmuCp7qfosMSKX/Dxc9OHm9gYcxHZ8yiIATDk=; b=IAzwug9fAikSJX8x27oikpnEX8nfnOeELoRFB1DAS82v5p8e6enJmA4LB8gpSz2iug GJ8++lA8Sn4ErdhO/vycMZxUoJb4CjnkJR95YdraEuG4PHrvUqKM2YbV+IztWxotM4N+ PV6NTz9YAtYG6SO+B0TrspRU/Da9H0WsJKMtM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=pk+48vZBlGTl2mnrQMXLCVlMZCs2PBYB55HJuPpmNWsL9EoDf5dpLQbJAmQUUkz0fz B8O49vxkM3XkAWybj1c5TePpsmHCGkoA+speI599DkQqt36m66qWVlRgV3h2dyFl9fMW 9BHzxPEDdBHumKpkr1ApwIoQVxOsPd6y0Ro7k= MIME-Version: 1.0 Received: by 10.216.140.15 with SMTP id d15mr1492136wej.64.1301122061360; Fri, 25 Mar 2011 23:47:41 -0700 (PDT) Received: by 10.216.164.212 with HTTP; Fri, 25 Mar 2011 23:47:41 -0700 (PDT) In-Reply-To: <201103241651.p2OGpuSK090082@givry.fdupont.fr> References: <201103241651.p2OGpuSK090082@givry.fdupont.fr> Date: Sat, 26 Mar 2011 15:47:41 +0900 Message-ID: From: =?ISO-8859-1?Q?Jehan_Pag=E8s?= To: Francis Dupont Cc: caml-list Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Caml-list] Ocaml and cryptography Hi, I see. Indeed I checked OpenSSL, it is using massively assembly code for SHA1 and many other (all?) crypto code... And my tests on a 64 bits machine and the huge improvement for OpenSSL there makes me think that they must be making very good use of the 64 bits register for saving the 32 bits words of SHA1 algorithm (they probably make some calculation on 2 words at once thanks to this). Jehan 2011/3/25 Francis Dupont : > This is not the first study about crypto implementation speeds. > Usually the winner for heavily used algorithms is OpenSSL, > BTW not because it is well written but simply because it is > optmized in assembly for common platforms (including SSE* & co > on x86). > > Regards > > Francis.Dupont@fdupont.fr >