[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120501050420.GA10374@openwall.com>
Date: Tue, 1 May 2012 09:04:20 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: Lukas - status report #2
Lukas -
On Tue, May 01, 2012 at 08:37:02AM +0400, Solar Designer wrote:
> On Tue, May 01, 2012 at 06:13:01AM +0200, Lukas Odzioba wrote:
> > 2012/5/1 Solar Designer <solar@...nwall.com>:
> > > user@...l:~/john/magnum-jumbo/run$ ./john -te -fo=wpapsk-opencl -pla=1
> > > OpenCL platform 1: AMD Accelerated Parallel Processing, 2 device(s).
> > > Using device 0: Tahiti
> > > Optimal Group work Size = 128
> > > Benchmarking: wpapsk-opencl [pbkdf2-sha1]... DONE
> > > Raw: 64000 c/s real, 531692 c/s virtual
> > >
> > > This is quite nice. hashcat is reported to do 158.1k c/s on 5970, so
> > > our target speed for 7970 may be about 130k c/s.
> >
> > I would be more happy to see 80-90k, previously (just pmk calculation
> > - most time consuming) we had 90% of hashcat's speed. For now
> > difference will be ever worst for super fast gpus and slow cpu.
> > Besides cpu side code utilizes only 1 core. Do you have any ideas to
> > get around it other than MPI? On the other side we could move all code
> > to second kernel gpu.
>
> I don't understand what you're referring to. I just took a look at
> opencl_wpapsk_fmt.c and I don't see it doing much on the CPU. Can you
> point me at specific places in the code?
>
> Do you think my run on the 7970 was somehow CPU-bound? I doubt it.
I tested and looked at the code in magnum-jumbo from a few hours ago.
It turns out that you made an important commit in those hours. I'll
re-test and re-review.
Alexander
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.
