[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKGDhHWzY7JSGk64twA7-xbKNv127ksCUymUDP9WaQbMKN4XMA@mail.gmail.com>
Date: Sat, 4 Apr 2015 16:44:44 +0200
From: Agnieszka Bielec <bielecagnieszka8@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: [GSoC] John the Ripper support for PHC finalists
2015-04-03 20:32 GMT+02:00 magnum <john.magnum@...hmail.com>:
>It's not just auto tuning. Unless I misunderstand the problem, the very
>function you need is reset(). For example like this:
>- On reset(NULL), as in self-test, you set some fixed low LWS/GWS of eg.
>32/128 and whatever mem_size is needed for test vectors' costs. Yes, you
>will get an extra compile here, but that's faster than a self-test with
>full LWS/GWS anyway.
>- On reset(db), you parse the db and see what costs you actually need.
>Then you release the temporary buffers/kernel, and auto-tune using the
>costs that are actually needed (you can even auto-tune with the very
>hashes loaded for cracking, which should be optimal).
>BTW compiled kernels will be cached. For nvidia the driver caches it.
>For AMD, we do.
thanks but what about --test command? before --test reset() is called
with db=NULL and tests are for fixed m_cost and t_cost
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.
