Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2b576f028e1608cea5ff321285567b08@smtp.hushmail.com>
Date: Mon, 29 Sep 2014 20:07:17 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: NVIDIA GTX 970 (Maxwell 2 / GM204) opencl benchmarks

On 2014-09-29 06:44, Royce Williams wrote:
> Sayantan said that GTX 970 benchmarks might be useful for john-dev, so
> here are opencl-specific benchmarks for the EVGA model 04G-P4-0972-KR,
> non-overclocked.

Yes, thanks!

>  I wrote a quick wrapper to only run --test for the the *-opencl formats

Maybe you are not aware that you can use --format=opencl which will do 
just that. You can also use --format=cuda or do both with --format=gpu. 
You can even use a wildcard, as in --format=wpapsk* for testing all 
variants of that format, or --format=*crypt for all formats that ends in 
"crypt".

> The test system's current CPU (Sempron 145, sorry) is woefully
> underpowered for any CPU-fed formats.  A better chip is on its way,
> and I can test again if needed.  The JtR build is from a Sep 27
> download bleeding-jumbo; I can run a different version if needed.
> NVIDIA drivers are 343.22.

I'd much appreciate a benchmark before/after trying this change: In 
src/opencl/wpapsk_kernel.cl (and many others, but lets try this first), 
we have this:

	#if gpu_amd(DEVICE_INFO)
	#define USE_BITSELECT
	#endif

If you delete the #if and #endif so we define it for nvidia too, does it 
affect performance significantly? Note that after editing, you need to 
run "make" to have the change "activated" even though the kernel is 
built at run-time.

magnum

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.