[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <507310BB.2040405@gentoo.org>
Date: Mon, 08 Oct 2012 13:43:23 -0400
From: "Rick \"Zero_Chaos\" Farina" <zerochaos@...too.org>
To: john-users@...ts.openwall.com
Subject: Re: CUDA tweaking to your actual GPU
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/08/2012 01:17 PM, magnum wrote:
> On 8 Oct, 2012, at 18:11 , Solar Designer <solar@...nwall.com> wrote:
>
>> On Mon, Oct 08, 2012 at 11:40:40AM -0400, Rick Zero_Chaos Farina wrote:
>>> So can we do the same for cuda then?
>>
>> The same == what? Several things have been mentioned. Anyhow, I and
>> others in here understand that distros want to be able to have a single
>> mostly-binary build that is near-optimal for a wide range of systems.
>> We do have this in mind.
>>
>>> This is what hashcat does now as well.
>>
>> As far as I'm aware, hashcat uses precompiled kernels with both OpenCL
>> and CUDA - perhaps many for each hash type, yes (for different GPUs).
>
> Why would you want precompiled kernels for a distro though? I assume Hashcat does this mostly for protecting its source code - which we do not need (nor want) to. There are obvious benefits with run-time compilation, and *especially* for distros. It was designed that way for a reason. If you'd make a "jumbo-opencl" package from our current tree, with dependecies of *any* opencl framework package(s), the end user will be able to run it even if his/her hardware (and drivers/framework) are newer than the JtR package itself.
I recall seeing some sm_10 or something in the sources suggesting to
change to 20 or 30 or whatever depending on hardware. Please don't
shoot me if I'm wrong, I freely admit I'm not looking right now but I
bet you know what I'm talking about.
>
> I think we have other important tasks for distros though: Apart from the license mess... I'm not sure our current placement of OpenCL and CUDA headers and sources - in the run directory - works at all with a systemwide build. Has anyone tried that? Will they currently end up in the systemwide bin directory or in ~/.john? Will the OpenCL or CUDA program find them at all?
*.cl ends up in /etc and john finds it fine. Gentoo has been shipping
opencl/cuda enabled jtr since it was released.
Thanks,
Zero
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQIcBAEBAgAGBQJQcxC7AAoJEKXdFCfdEflK2PgP/jH8Pg+Gn45Em/rhc0MnSB9Y
Rlp6oMBL3qKBuzUm2uFMKvPY1zlz9xD5K18KO8y9JptFpKI9dletjRc9e5xlbtQ7
4PQvxzrr+yIZX0/YFp3CDKP0uebBrjH0d0IArw0LaoKA7Gt6DP8pVUhRE3HNvqx1
5qMHxKCnBarpFHY+4hE6Ku25X6q0b+kOibn879ZIuoF22kFr2NrWJQwDB+nRqBYk
6IHXL5S3OHQuzDuOnRAKm3nviAQvsW3lxFfRShdz6IumdkZzeAzY+Api7wHH5c54
QZVlhbi4p2hGOQkb1IbV5ETBOlzIe4yXpTqYzPuHEi+eXea9M8F/xp5BDzUkmbXD
OvWqGKYJQwtNFziE2RYkxS6DY+Z83v5HReVCZuN3tNDAvInjy7edd1N+DQkg9JT3
5Pkrxg6Etoy3eIEkq3Mz7NN7aRR7IQueINA9sZLs61CojUsOM0vTk5rt+y7932Ue
aEEdtAzv4XcDztSCgVlcX5mqv6wmIyJ+I7OUJCJ7MFp671hiRDY+nT1UngwtL+b9
faBKJdE90PxArJoHpyB0LbLlSQrry6WplFlLhhVRxNMzTrV7ytwglsXZkgvSiOha
/Mm8oUR4rBcaasC7QwXnHhdGSJLEKomjwcuL/TEJRghTuoWh/MKmDFV6NyKJJqbN
/8O7ZY2dsrjIQscIVAQf
=3TAu
-----END PGP SIGNATURE-----
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.
