[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7ef822c97496203df22ac5f8181ad638@smtp.hushmail.com>
Date: Fri, 5 Jul 2013 01:24:12 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: bug: GPU use in CPU-only formats
On 4 Jul, 2013, at 21:49 , magnum <john.magnum@...hmail.com> wrote:
> On 4 Jul, 2013, at 20:41 , magnum <john.magnum@...hmail.com> wrote:
>> I'm starting to think we should drop that branch and try to straighten things out properly. Here's what I think we should do:
>>
>> 1. (This is a side track) Re-factor all non-static functions in common-opencl.c so they are prefixed with opencl_, eg:
>>
>> init_opencl_devices() -> opencl_passive_init()
>> clean_opencl_environment() -> opencl_done()
>>
>> 2. Re-work opencl_passive_init() so it does the platform/device enumeration and option parsing but does *not* set up any queue or context (I am confident that's what wakes up the GTX 570).
>>
>> 3. Add such setting up of queue and context in opencl_init_opt().
>>
>> And then we keep calling opencl_passive_init() from john.c but it won't wake up the nvidia. I'll think this over for a while.
>
> I tried this in yet another temporary branch "opencl-init2". It does not work. Again, probably something really trivial and I'm just unfocused.
Fixed now, and committed to main tree in 1c46af2. I'm looking into some weirdness with mscash2-opencl when using multiple devices, I may have to tweak something.
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.
