[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50F2CD83.9090807@gmail.com>
Date: Sun, 13 Jan 2013 13:06:43 -0200
From: Claudio André <claudioandre.br@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: SIGALRM and new 'done' method
Em 13-01-2013 00:32, magnum escreveu:
> This was a problem even in unstable: After a wad of patches tonight,
> dang near all formats honour LWS and GWS environment variables. That
> means we can now do this for a quick full self-test (with inaccurate
> speed figures) even for OpenCL and/or CUDA builds:
Does CUDA has a proper done method?
> $ LWS=3 GWS=33 ./john --test=0
>
> BTW I have used this with LWS=1 and GWS as a prime, as well as LWS as a prime and GWS=$((LWS*7)) trying to trigger array bugs, but none were found.
>
> Oh, and the only formats not honouring these environment variables are Sayantan's DES, BF and MScash2 because I don't want to make a mess of them, but I'd really like this support to be added. It is invaluable for testing and for using weaker devices than the formats expect.
Sayantan, are you available? To tell the truth, i did (really) small
changes inside some of this files. But there are hard work to be done.
As I said before, to use it properly in my branch, i need a proper done
method in all these files.
It will be nice if we can port DES, BF and MScash2 to use this new
devices, platforms, ..., (from the new common-opencl.c), LWS, GWS.
> But I digress. This revealed that the problem you saw exist in unstable-jumbo too, so I did some more head-scratching and ended up realizing my last patch was the right way of handling it, but it did not support all kinds of systems. It does now, problem solved. No workarounds, just a correctly restarting signal handler.
Very good. Will try to merge it soon.
Claudio
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.
