Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50F2F481.30103@gmail.com>
Date: Sun, 13 Jan 2013 15:53:05 -0200
From: Claudio André <claudioandre.br@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Changes to common-opencl.c

Em 13-01-2013 13:28, magnum escreveu:
> Actually the more I think about it, the less I want that header device list or platform info at all (when you need it, we have --list=opencl-devices). So no output at John init, and only this line at each*format*  init:
>
> Using device 0: Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz
>
> or for multiple devices:
>
> Using device 1: Tahiti
> Using device 2: Tahiti
> Using device 3: Tahiti
> Using device 4: Tahiti
>
> For comparison, oclHashcat outputs this:
>
> Device #1: Cayman, 1024MB, 800Mhz, 24MCU
> Device #2: Cypress, 512MB, 800Mhz, 20MCU
> Device #3: Cayman, 1024MB, 800Mhz, 24MCU
> Device #4: Cypress, 512MB, 800Mhz, 20MCU
>
>
> This also solves the strstr() discussion - just init quitely and never output that stuff at all!
>
> Also, I think this "Using device" line needs to be printed for every OpenCL format in a --test (all) run, contrary to what I said earlier. Because otherwise we'll have another caveat: What should happen if we say "./john --test=0 --devices=gpu"? Let's say the first OpenCL format that benchmarks can handle one device, so we'll get "Using device 1...". Later, the mscash2 format benchmarks and use all devices, so we need new output showing that.
>
> magnum

Commited.
---

BTW: I changed listOpenCLdevices.
Could you please test it latter? You put a lot of specialized 
information there and i don't have the hardware.

Claudio


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.