[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150826230700.GA12582@openwall.com>
Date: Thu, 27 Aug 2015 02:07:00 +0300
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: LWS and GWS auto-tuning
On Thu, Aug 27, 2015 at 01:01:27AM +0200, magnum wrote:
> Max Work Group Size: 8192 <---- here!
> Parallel compute cores: 8
>
> I'm do not think the de-facto limit of 1024 we've been used to is an
> actual maximum per any specifications. Also, when I tried this it ran
> just fine through the tests up to 8192 but picked a lower number as
> best. If it wasn't actually supported, we should get an
> CL_INVALID_WORK_GROUP_SIZE error and it would have been caught and
> handled properly.
>
> I presume your segfault was unrelated to the work size.
OK. There was also "OpenCL error (CL_INVALID_VALUE) in file
(opencl_cryptmd5_fmt_plug.c) at line (381) - (Copy data back)".
Are you going to look into these, or/and create GitHub Issues so they
are not forgotten?
Alexander
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.
