Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 2 Nov 2014 08:59:22 -0900
From: Royce Williams <royce@...ho.org>
To: john-dev <john-dev@...ts.openwall.com>
Subject: Re: descrypt speed

On Thu, Oct 30, 2014 at 9:33 PM, magnum <john.magnum@...hmail.com> wrote:

> On 2014-10-31 06:02, Royce Williams wrote:
>
>>

> Going back through my config/make cycle, I didn't notice this at first:
>>
>
>> ptxas info    : Compiling entry function
>> '_Z13kernel_phpassPhP12phpass_crack' for 'sm_20'
>>
>> In fact, all of the appearances of sm_[0-9+] in my ./configure and
>> make results appear to be using sm_20.  Strings on the john binary
>> only shows sm_20 in use.
>>
>> On a GTX970, shouldn't this be sm_52?
>>
>
> You can force this by editing NVCC_FLAGS in Makefile. Add something like
> "-arch sm_50" (or 52). But I doubt it will make much difference and it will
> only affect CUDA formats.


In my system with both an sm_20 and an sm_50 card, when running solely
descrypt-opencl (not CUDA), the ptxas info shows that sm_50 is involved in
some way.  Is this cosmetic?

$./john --fork=2 --format=descrypt-opencl
/home/royce/projects/yestercrack/shadow.ken
Loaded 1 password hash (descrypt-opencl, traditional crypt(3) [DES OpenCL])
Node numbers 1-2 of 2 (fork)
Device 1: GeForce GTX 480
Device 0: GeForce GTX 750 Ti
Build log:
ptxas info    : 0 bytes gmem
ptxas info    : Compiling entry function 'DES_bs_25_b' for 'sm_50'
ptxas info    : Function properties for DES_bs_25_b
ptxas         .     256 bytes stack frame, 0 bytes spill stores, 0 bytes
spill loads
ptxas info    : Used 77 registers, 15876 bytes smem, 348 bytes cmem[0]
Build log:
ptxas info    : 0 bytes gmem
ptxas info    : Compiling entry function 'DES_bs_25_b' for 'sm_20'
ptxas info    : Function properties for DES_bs_25_b
ptxas         .     264 bytes stack frame, 0 bytes spill stores, 0 bytes
spill loads
ptxas info    : Used 63 registers, 15876 bytes smem, 60 bytes cmem[0]
Local worksize (LWS) 64, Global worksize (GWS) 16384
Local worksize (LWS) 64, Global worksize (GWS) 16384

Royce

Content of type "text/html" skipped

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.