From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 94EB57EE25 for ; Tue, 19 Nov 2013 23:40:08 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of ecc@cmu.edu) identity=pra; client-ip=128.2.217.198; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="ecc@cooper-siegel.org"; x-sender="ecc@cmu.edu"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of ecc@cooper-siegel.org) identity=mailfrom; client-ip=128.2.217.198; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="ecc@cooper-siegel.org"; x-sender="ecc@cooper-siegel.org"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@smtp03.srv.cs.cmu.edu) identity=helo; client-ip=128.2.217.198; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="ecc@cooper-siegel.org"; x-sender="postmaster@smtp03.srv.cs.cmu.edu"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjACAGTni1KAAtnGnGdsb2JhbABZgz/BNBYOAQEBAQEICwkJFCiCJQEBBTpPCxgJExIPBRiIRQ23Yogaj3SEHAOJQo5PlVQ X-IPAS-Result: AjACAGTni1KAAtnGnGdsb2JhbABZgz/BNBYOAQEBAQEICwkJFCiCJQEBBTpPCxgJExIPBRiIRQ23Yogaj3SEHAOJQo5PlVQ X-IronPort-AV: E=Sophos;i="4.93,732,1378850400"; d="scan'208";a="43921242" Received: from smtp03.srv.cs.cmu.edu ([128.2.217.198]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Nov 2013 23:40:07 +0100 Received: from stratocaster.home (pool-96-236-201-222.pitbpa.fios.verizon.net [96.236.201.222]) (authenticated bits=0) by smtp03.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id rAJMe3Q5016863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 19 Nov 2013 17:40:05 -0500 (EST) Received: by stratocaster.home (Postfix, from userid 1000) id 6A4A01D0667D; Tue, 19 Nov 2013 17:39:32 -0500 (EST) Date: Tue, 19 Nov 2013 17:39:32 -0500 From: Eric Cooper To: caml-list@inria.fr Message-ID: <20131119223932.GH10034@cooper-siegel.org> Mail-Followup-To: caml-list@inria.fr References: <20131118204426.GA14731@annexia.org> <1384819720.4083.57.camel@zotac> <1384859953.62343.YahooMailNeo@web120403.mail.ne1.yahoo.com> <20131119125519.GA18044@ccellier.rd.securactive.lan> <528BE3C3.2050304@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <528BE3C3.2050304@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Scanned-By: mimedefang-cmuscs on 128.2.217.198 Subject: Re: [Caml-list] Hardening [Perl's] hash function further On Tue, Nov 19, 2013 at 11:18:43PM +0100, Nicolas Braud-Santoni wrote: > I am not aware of instruction sets dedicated to speeding up hash > functions (unlike encryption with AES, for instance). But many systems-on-chips have crypto engines that can be used for this purpose. See http://www.marvell.com/application-processors/armada-500/ to cite just one example. -- Eric Cooper e c c @ c m u . e d u