[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <40c39bac2b6b39279e3cadcaaf539613@smtp.hushmail.com>
Date: Wed, 08 Jul 2015 14:35:50 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: PHC: Lyra2 on GPU
On 2015-07-08 14:27, Solar Designer wrote:
> On Wed, Jul 08, 2015 at 01:40:59PM +0200, magnum wrote:
>> Solar, Sayantan,
>>
>> I'm contemplating another change: For benchmark, we can build a little
>> fake db that contains whatever test-vectors will be used (and obviously
>> pass that). This will simplify the formats' code not only for Agnieszka
>> but also for eg. Sayantan's GPU-side mask/compare formats. There would
>> be no need for benchmark kludges in the formats. This would also support
>> things like "--test --cost=xx" with no special code in the formats.
>
> This is something I would recommend for Kai's extensive self-test, and
> to build that self-test on top of calls to cracker.[ch] functions.
>
> As to changing our existing "quick" self-test like that, I am not sure.
I'm talking about benchmark, not self-test. I think getting things like
"benchmark Pomelo, using this cost" or "benchmark raw-sha256-opencl
using GPU-side mask-mode" will be extremely hacky, in each format,
without doing this.
magnum
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.
