Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 2 Feb 2012 08:04:13 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: OpenCL vs Test Suite

On Sat, Jan 28, 2012 at 03:50:25PM +0100, Samuele Giovanni Tonon wrote:
> this due to the buffer i send to the GPU that needs to be "prepared"
> before in the init function :
> 
> buffer_keys =
>             clCreateBuffer(context[gpu_id], CL_MEM_READ_ONLY,
>             (SHA_BLOCK) * SSHA_NUM_KEYS, NULL, &ret_code);

Do you gain much by keeping this fixed size?  Maybe adapt the block size
to the maximum password length actually seen in the current block (which
may vary from block to block)?  That way, the GPU can start processing
the candidate passwords in parallel right away (without having to scan
the buffer sequentially first, like it would with a more advanced
encoding scheme), yet the transfer size is reduced and the maximum
supported password length is increased.

Alexander

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ