[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 13 Jun 2011 21:36:54 -0300
From: Yuri Gonzaga <yuriggc@...il.com>
To: crypt-dev@...ts.openwall.com
Subject: Re: EskBlowFish with RAM results
>
> The first thing to do is exclude all code that is not in the performance
> critical loop, as discussed before.
Done!
> Even though I don't really know Verilog, I took a look at the code,
> thanks. It appears that you spend 5 clock cycles per Blowfish round:
> 1. L xor P[n]
> 2. read two S-box elements
> 3. process them, read two more S-box elements
> 4. process them
> 5. swap L and R, move to next round
> I think you could reduce this to three (while still using two read ports
> to BlockRAM only):
> 1. L xor P[n], read two S-box elements
> 2. process them, read two more S-box elements
> 3. process them, swap L and R, move to next round
Done! But, as the following results (http://bit.ly/mOP15y) state, the LUT
resources tend to grow.
Regards,
Yuri
Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
