Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 30 Aug 2013 08:13:01 +0530
From: Sayantan Datta <std2048@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Sayantan Weekly Report #11

Hi magnum,

On Fri, Aug 30, 2013 at 3:21 AM, magnum <john.magnum@...hmail.com> wrote:

> I meant it's poor on this GPU regardless of that bugfix patch. 57M is just
> three times faster than one CPU core.
>
> Here's a theory: Since mask mode currently picks 26*26 == 676 as
> multiplier in this case, I have no choice other than to lower GWS all the
> way to 16384 (ending up in a KPC of 11075584) to keep kernel duration short
> enough to avoid triggering watchdogs and rebooting the whole thing. I
> presume the "low" GWS is the reason for the poor performance. Maybe it
> would be way better with a multipler of 26 and a GWS of 524288... in *this*
> case.
>
> Maybe the kernel can be improved (reducing need for high GWS) but
> regardless of that, this means auto-tuning will be trickier: You need to
> figure out not only the GWS but the best *combination* of GWS and GPU-side
> mask that completes in less than 200ms.
>

You can set db->max_int_keys=26 in reset. This will limit multiplier to 26.
Yes, device tuning can be a bit tricky. Also, it is not possible to tune
mask settings in runtime with the current version. I'm hoping to fix the
issue in this week.

Regards,
Sayantan

[ CONTENT OF TYPE text/html SKIPPED ]

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ