[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 16 Sep 2013 23:55:31 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: --fork using different OpenCL devices
On 16 sep 2013, at 17:27, magnum <john.magnum@...hmail.com> wrote:
> This turns out to be very tricky to implement properly because the format (and therefore the OpenCL stuff) is initialized before forking. We need to postpone that, or de-init/re-init after fork() and I haven't managed to pull it together correctly just yet.
It seems I got it working with --fork too now:
$ ../run/john test.in -form:rar-opencl -fork=3 -dev=gpu -inc:digits -max-len=6
Loaded 1 password hash (rar-opencl, RAR3 [SHA1 AES OpenCL])
Node numbers 1-3 of 3 (fork)
Device 4: GeForce GTX TITAN
Device 0: Tahiti (AMD Radeon HD 7900 Series )
Device 1: Tahiti (AMD Radeon HD 7900 Series )
Local worksize (LWS) 64, Global worksize (GWS) 65536
Local worksize (LWS) 64, Global worksize (GWS) 65536
Local worksize (LWS) 64, Global worksize (GWS) 131072
Press 'q' or Ctrl-C to abort, almost any other key for status
2 0g 0:00:00:27 108.35% (2013-09-17 01:45) 0g/s 13062p/s 13062c/s 13062C/s
1 0g 0:00:00:33 107.55% (2013-09-17 01:45) 0g/s 14689p/s 14689c/s 14689C/s
Waiting for 2 children to terminate
3 0g 0:00:00:23 DONE (2013-09-17 01:45) 0g/s 11219p/s 11219c/s 11219C/s
Session completed
This is somewhat experimental because I have to postpone format init and self-test until after forking. It seems to work just fine though. As long as you don't give both --fork and --device options at once, everything will be normal so hopefully if there are any problems they wont affect "normal" runs. And non-OpenCL builds are not affected at all.
On an unrelated note I guess I need to have a look at those percent figures o.O
magnum
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.
