[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F9E4767.9000007@linuxasylum.net>
Date: Mon, 30 Apr 2012 10:03:51 +0200
From: Samuele Giovanni Tonon <samu@...uxasylum.net>
To: john-dev@...ts.openwall.com
Subject: Re: Changes in common_opencl.c
On 04/30/12 01:05, Claudio André wrote:
> Hi, i created a CPU only kernel (a .cl new file). Keep everything in
> just one file was a nightmare.
>
> It is 10% better than John non Jumbo (crypt(3)), and, of course, worse
> than OpenSSL one.
>
> To do so, i had to change common_opencl.c, especially, to allow me "init
> opencl" and later "compile the kernel". I add new functions, existing
> code still works fine.
> I also added better suport for get CPU/GPU information: cpu(n), gpu(n),
> gpu_amd(n), gpu_nvidia(n), etc.
>
> Any complains? To understant, a patch snip:
i've taken a quick look to the code and i see no problem however
why not create an "opencl_init2" so people can choose to use it and test
it and if it's all good we all switch to this new interface ?
In this way we keep "backward compatibility" with the old interface
while letting people to try and test it .
Cheers
Samuele
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.
