Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <086501d06b9f$e31b8cb0$a952a610$@stricture-group.com>
Date: Tue, 31 Mar 2015 03:46:04 -0700
From: "Jeremi M Gosney" <jgosney@...icture-group.com>
To: <john-dev@...ts.openwall.com>
Subject: RE: [GSoC] John the Ripper support for PHC finalists

> -----Original Message-----
> From: magnum
> Sent: Monday, March 30, 2015 02:51
> 
> On 2015-03-30 11:11, magnum wrote:
> > Also, your auto-tune settings are totally wrong, possibly ending up in
> > suboptimal work sizes. I will fix them and submit a patch.
> 
> This patch fixes the auto-tune problems. BTW with my other suggestions
> it also runs fine on the GTX Titan, at about same ~10K c/s speed as on
> HD7970. And now it also runs on my Macbook GPU (1290 c/s).


I had to change "char build_opts[64]" to "char build_opts[64] = {0};" in init() in order to get this to run, otherwise it would fail with the following error:

OpenCL error (CL_INVALID_DEVICE) in file (common-opencl.c) at line (969) - (Error while getting build info I)

For some reason I'm seeing half the speeds you're seeing on 290X.

epixoip@...en:~/pomelo/JohnTheRipper/run$ ./john -te -form:pomelo-opencl
Device 0: Hawaii [AMD Radeon R9 200 Series]
Local worksize (LWS) 64, global worksize (GWS) 1024
Benchmarking: pomelo-opencl, POMELO [POMELO OpenCL (inefficient, development use only)]... DONE
Raw:    5535 c/s real, 614400 c/s virtual



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.