caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Hardening [Perl's] hash function further
Date: Mon, 25 Nov 2013 14:46:30 +0100	[thread overview]
Message-ID: <20131125134630.GE3610@frosties> (raw)
In-Reply-To: <528BEC6B.4090300@gmail.com>

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

  reply	other threads:[~2013-11-25 13:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 20:44 Richard W.M. Jones
2013-11-19  0:08 ` Gerd Stolpmann
2013-11-19  7:53   ` David MENTRE
2013-11-19  8:50     ` Richard W.M. Jones
2013-11-19  9:14     ` Gabriel Scherer
2013-11-19 11:19       ` Dario Teixeira
2013-11-19 12:55         ` rixed
2013-11-19 22:18           ` Nicolas Braud-Santoni
2013-11-19 22:39             ` Eric Cooper
2013-11-19 22:55               ` Nicolas Braud-Santoni
2013-11-25 13:46                 ` Goswin von Brederlow [this message]
2013-11-19 22:31         ` Nicolas Braud-Santoni
2013-11-20 18:56         ` Florian Weimer
2013-11-20 21:47           ` Gerd Stolpmann
2013-11-25 13:51             ` Goswin von Brederlow
2013-11-25 14:43               ` Yaron Minsky
2013-11-19 22:15     ` Nicolas Braud-Santoni
2013-11-25 13:38   ` Goswin von Brederlow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131125134630.GE3610@frosties \
    --to=goswin-v-b@web.de \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).