[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <da8695614c9b08d6b6214a8b9df50739@smtp.hushmail.com>
Date: Sat, 25 Apr 2015 20:44:26 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: [GSoC] JtR SIMD support enhancements
On 2015-04-25 20:21, Solar Designer wrote:
> Speaking of OpenMP in particular, as you know it's inefficient for fast
> hashes, so for those I'd tune the interleave factors with -fork instead.
Since we currently can't have different interleaving factors for
different formats using same primary hash function, I think it's most
sensible to simply tune for md5rypt, wpapsk and so on. I have seen a few
cases where raw-md5 and md5crypt had different best factor, but it was
insignificant - and md5crypt is the arbitrator IMO.
For MD4 we might actually want to tune for raw-md4 or NT2 though, using
fork like you say.
I guess Lei compiled with --disable-openmp-for-fast-formats, virtually
all formats can do OpenMP now even though it's not always sensible. BTW
even for fast formats I have a feeling we might want to compare 59 forks
x 4 threads with simply 236 threads. Wouldn't that have better chance to
run optimally? Though maybe you've already said that at some point and
that's why I get this gut feeling :-)
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.
