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 E11607EE6B for ; Mon, 25 Nov 2013 14:46:31 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of goswin-v-b@web.de) identity=pra; client-ip=212.227.17.12; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="goswin-v-b@web.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of goswin-v-b@web.de) identity=mailfrom; client-ip=212.227.17.12; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="goswin-v-b@web.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mout.web.de) identity=helo; client-ip=212.227.17.12; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="postmaster@mout.web.de"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjwCACxUk1LU4xEMnGdsb2JhbABZgz+3LIVOgSsWDgEBAQEBBg0JCRQogiUBAQU6TwsYCSUPBSiIIgEWCbUFH4hcjw4WgwqBEwOYE4YuEo58 X-IPAS-Result: AjwCACxUk1LU4xEMnGdsb2JhbABZgz+3LIVOgSsWDgEBAQEBBg0JCRQogiUBAQU6TwsYCSUPBSiIIgEWCbUFH4hcjw4WgwqBEwOYE4YuEo58 X-IronPort-AV: E=Sophos;i="4.93,768,1378850400"; d="scan'208";a="45242273" Received: from mout.web.de ([212.227.17.12]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 25 Nov 2013 14:46:31 +0100 Received: from frosties.localnet ([37.49.32.119]) by smtp.web.de (mrweb101) with ESMTPSA (Nemesis) id 0MKrLo-1VkwUh09WS-0003Kv for ; Mon, 25 Nov 2013 14:46:31 +0100 Received: from mrvn by frosties.localnet with local (Exim 4.80) (envelope-from ) id 1VkwUg-0001nm-DY for caml-list@inria.fr; Mon, 25 Nov 2013 14:46:30 +0100 Date: Mon, 25 Nov 2013 14:46:30 +0100 From: Goswin von Brederlow To: caml-list@inria.fr Message-ID: <20131125134630.GE3610@frosties> 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> <20131119223932.GH10034@cooper-siegel.org> <528BEC6B.4090300@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <528BEC6B.4090300@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Provags-ID: V03:K0:tj2bwTcUHP9P94jXGBDXv3XuRQZVP5cBH+IH4BgarC/JxvpTHfJ LchFQGkIGYUu0zfepljsR9v1oV5Ku1LRJBulXwJUg2KeqPySh25AN+YTM5qXhRu+QOprmLR 9UdpPPh1ikQ3kPLEyh36D9aEF7dxocX4wf/HsV21n7rDy56NZT9G6nk+Er2rU4YWB3BbdSK xKsWUOkpUpcgQne3r58lA== Subject: Re: [Caml-list] Hardening [Perl's] hash function further On Tue, Nov 19, 2013 at 11:55:39PM +0100, Nicolas Braud-Santoni wrote: > On 19/11/2013 23:39, Eric Cooper wrote: > > 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. > Using SoC-specific hardware accelerators is probably way out-of-scope > here :-) I also think that hashtable keys are usualy too small by several magnitudes to benefit from it. The cost of setting up the hardware crypto engine from userspace will be way higher than hashing e.g. 64 byte yourself. I would expect that anything below page size at least won't be faster in hardware but that is just a guess. MfG Goswin