Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 15 Jun 2013 21:31:47 +0530
From: Sayantan Datta <>
Subject: Re: Mask mode for GPU

On Saturday 15 June 2013 08:15 PM, Solar Designer wrote:
> For example, in a given kernel invocation the host might provide strings
> "aaaaaa.." to "aaaapq..", where ".." are any placeholder chars, which
> the GPU will overstrike anyway, and the GPU (separately in each
> work-item) will iterate from "aa" to "zz" in the last two character
> positions.  On the next kernel invocation, the host will start with
> "aaaapr..".  (By choosing the weird end/start of range for these two
> kernel invocations, except for the very first invocation's range start,
> I illustrate that they don't have to be at prettier looking points in
> the keyspace, and in practice they generally won't be.  Just whatever
> fits in the optimal GWS.)
Okay. So to summarize the set_mask() should generate some portion of the 
mask on cpu and some portion on gpu depending on GWS or hash per kernel 
invocation.  Positions where gpu will overstrike the keys will depend on 
the number of available characters at those positions so that it is 
enough for all work items.


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.