[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+TsHUBXfurzadPiTB24n9VEu8MZ_mdnPtsN9Wvb_06_TZ4RkQ@mail.gmail.com>
Date: Wed, 19 Sep 2012 17:42:40 +0530
From: Sayantan Datta <std2048@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: bitslice DES on GPU
Hi Alexander,
On Fri, Sep 14, 2012 at 2:02 AM, Solar Designer <solar@...nwall.com> wrote:
> So that's about 41M c/s at 25 iterations if you somehow manage to remove
> the overhead. In other words, the overhead still corresponds to about
> 50% of total running time.
>
I'm trying to figure out where the overhead lies. I thought it might be the
cmp_all() function. So I tried using openmp in cmp_all. However there was
no improvement at all. This makes me think that the overhead lies primarily
in set_key which is called maximum number of times. Can you provide any
suggestions? How about doing the set key in GPU using another kernel?
Regards,
Sayantan
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.
