Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150307152556.GA17352@openwall.com>
Date: Sat, 7 Mar 2015 18:25:56 +0300
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: [GSoC] building JtR for MIC

On Sat, Mar 07, 2015 at 11:15:57PM +0800, ??? ??? wrote:
> I managed to build JtR for MIC on a server in our lab, and get it running the benchmark. 

Great.

> The version of JtR I downloaded is 1.8.0. I added a target for MIC in the Makefile and created file mic.h (copied from ia64.h) to get it built for MIC. The model of Intel MIC card used is 5110P.

This is basically duplicate work to what I reported on here:

http://www.openwall.com/lists/john-dev/2015/03/05/2

That's fine.

> Below is the result of the benchmark:
> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????
> Benchmarking: descrypt, traditional crypt(3) [DES 64/64]... DONE
> Many salts:	179008 c/s real, 179008 c/s virtual
> Only one salt:	172812 c/s real, 172812 c/s virtual

This is just one core running the non-SIMD code.

> Any suggestions?

Since the core tree uses SIMD for bitslice DES only, and since we
already have MIC intrinsics for it (see my posting referenced above), in
the GSoC project you'd need to work solely with the jumbo tree.

So please try to get jumbo to build for and run on MIC, and report back
in here.  Ideally, magnum should merge my MIC support changes referenced
above into jumbo first, but this is not crucial since you clearly have
the experience to start without that as well.

https://github.com/magnumripper/JohnTheRipper

You may also experiment with 1.8.0.4 (from CVS, or I may send you the
tarball), just to have something inbetween your clean 1.8.0 build and
the jumbo build.

Thanks,

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.