Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 21 Sep 2013 17:22:03 +0200
From: Katja Malvoni <kmalvoni@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: ZedBoard / Parallella: bcrypt

Hi Alexander,

On Sat, Sep 21, 2013 at 12:36 AM, Solar Designer <solar@...nwall.com> wrote:

> Yes, something weird is going on.  Can you calculate the expected c/s
> rate for your current bcrypt IP core e.g. at 100 MHz, then figure out
> the actual clock rates from that?


Computation takes 2779846 clock cycles so expected c/s rate is 54 c/s for
150 MHz and 36 c/s for 100 MHz (not including communication overhead).
Clock rate influences communication as well because DMA and buses are
connected to the same clock as bcrypt IP.


> What's the maximum clock rate for
> which timing constraints are met?
>

I don't know yet, I'm trying 125 MHz at the moment.

Katja

Content of type "text/html" skipped

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ