[<prev] [next>] [day] [month] [year] [list]
Message-ID: <51D5DE28.9020206@gmail.com>
Date: Thu, 04 Jul 2013 17:42:16 -0300
From: Claudio André <claudioandre.br@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: bug: GPU use in CPU-only formats
> On Tue, Jul 02, 2013 at 10:01:15PM -0300, Claudio Andr? wrote:
> > > > Can't we do all initial "opening" of anything GPU-related in the
> > > > format's init(), if the format is GPU-enabled, and not any sooner?
> > > >
> > > > Perhaps there's some implementation difficulty that I am missing.
> >
> > It is possible, but if the user ask for -dev=7, i have to check if there
> > is such device, counting all available devices in each platform (this is
> > why we need to do more than only parse the command line). On unstable,
> > -device is always related to only one platform (no need to care about
> > other platforms). On bleeding, -device is a sequential number.
>
> Why did we introduce this unneeded(?) complexity? Was anything wrong
> with unstable's numbering of devices? Why don't we revert to it now?
>
> I think we should revert, unless you somehow convince me otherwise.
I agree that the better approach is just revert it to what you guys are
comfortable with. It will only impact one of the Sayantan's format (the
multi GPU is going to be hard-coded, as it was in the past).
Everything else is going to work as they used to.
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.
