[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANJ2NMNtR4m=sA7LpBqs7CudzHTsbE_EB93gC8uYmBxJ9gPe_w@mail.gmail.com>
Date: Mon, 16 Jul 2012 18:15:44 +0800
From: myrice <qqlddg@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: xsha512-cuda & xsha512-opencl testing
On Mon, Jul 16, 2012 at 5:35 PM, Solar Designer <solar@...nwall.com> wrote:
> myrice -
>
> On Mon, Jul 16, 2012 at 04:10:01PM +0800, myrice wrote:
>> Unfortunately, after lukas's work on bull, I cannot run my cuda format on it...
>
> It's weird, mscash2-cuda worked, but xsha512-cuda did not. I've just
> rebooted bull, and xsha512-cuda works now.
>
> BTW, xsha512-cuda produces nasty sound at maybe 5 KHz or so - is this
> the frequency of PCIe transfers or global memory accesses or something
> like that?
>
Sound?? You hear that from PC beeper or audio output? It is weird and
should not happen. What the sound like?
>> This is result under xsha512-opencl with incremental mode.
>
> Which incremental mode, exactly? This matters. If the incremental mode
> is not locked to a specific password length (e.g., just length 8), then
> there's some overhead early on to switch between lengths. For quick
> runs (like a few minutes), this overhead is significant. So you should
> be using -i=all8 (locked to length 8 only). Is this what you used?
>
Yes, I use -i=All8. Sorry for leaking that.
Thanks
myrice
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.
