Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FF46761.3050601@gmail.com>
Date: Wed, 04 Jul 2012 12:55:13 -0300
From: Claudio André <claudioandre.br@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: OSX problems with Jumbo-6 OpenCL

Em 03-07-2012 21:12, magnum escreveu:
> It fixed a lot of cosmetical problems but main problem remains (see
> https://github.com/magnumripper/magnum-jumbo/issues/50  for details).
> This user has a device seemingly not capable of OpenCL 1.1 (it's a
> GeForce GT 330M) so this is likely caused by byte_addressable_store
> (anyone know if raw-md5-opencl needs that?). I asked him to move to this
> list instead of using "GitHub Issues", we'll see if he does.
>
> magnum

I removed the byte_addressable and self-tested here (.cl attached).

Can you test it? Do you have a MAC?
---------

Using device 1: AMD Phenom(tm) II X6 1075T Processor
Max local work size 1024 Optimal local work size 1024
(to avoid this test on next run do export LWS=1024)
Local work size (LWS) 1024, Global work size (GWS) 2097152
Benchmarking: Raw MD5 [OpenCL]... DONE
Raw:    18289K c/s real, 4653K c/s virtual

Using device 0: Juniper
Max local work size 256 Optimal local work size 256
(to avoid this test on next run do export LWS=256)
Local work size (LWS) 256, Global work size (GWS) 2097152
Benchmarking: Raw MD5 [OpenCL]... DONE
Raw:    35141K c/s real, 75595K c/s virtual



View attachment "md5_kernel.cl" of type "text/plain" (5508 bytes)

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.