[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130730004721.GA13093@openwall.com>
Date: Tue, 30 Jul 2013 04:47:21 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: Parallella: bcrypt
Katja,
On Sat, Jul 27, 2013 at 06:17:56PM +0200, Katja Malvoni wrote:
> On Sat, Jul 27, 2013 at 5:26 PM, Solar Designer <solar@...nwall.com> wrote:
> > Also, I wanted to ask you: why do you transfer our several inputs to the
> > Epiphany side code one by one? Why not do just one transfer per core,
> > of a struct containing all inputs?
>
> I decided to do that when I had troubles with transferring these inputs
> correctly (different offsets on Epiphany and host sides and bug with memory
> allocation that existed in old SDK) and never changed it. But at the moment
> there is no reason not to use struct.
Perhaps you should change your code to transferring just one struct?
I wouldn't be surprised if this gives us a few c/s extra.
Alexander
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.
