Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <819a61b10606010944u540dd08dn6b326000cbb005a0@mail.gmail.com>
Date: Thu, 1 Jun 2006 18:44:06 +0200
From: "Otheus (aka Timothy J. Shelling)" <otheus@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: beta MPI john patch against 1.7.2.

On 6/1/06, Randy B <aoz.syn@...il.com> wrote:
>
> Any particular MPI implementation you either espouse or recommend
> avoiding?  I personally have been using lam-mpi, but that was more of
> a random dart-board kind of selection than anything.


This will work with MPICH. I have heard mixed things about all MPI
implementations. MPICH is "designed" for portability. LAM-MPI has perhaps
better performance, so I'm told. OpenMPI, released late last year, is a
merger of 3 different impelementations. My recent trials (in November)
proved that it was not production ready.


RB
>
> On 5/31/06, Otheus (aka Timothy J. Shelling) <otheus@...il.com> wrote:
> > This is a (beta) patch for John 1.7.2 for use with MPI.  All of the
> > MPI-specific code is encapsulated by #ifdef MPI/#endif, so in theory
> this
> > can be integrated into the main code branch. However, a few generic
> changes
> > to the code are also made.
> >
> > Please let me know of any rejects while performing the patch. (Use -l to
> > ignore whitespace to avoid problems with bench.c.)
> >
> > Changes:
> >   o  internalized computing the checksum for ext_word. 15% increase in
> speed
> > (at least)
> >   o  makes sure options required for MPI are present
> >   o  computes MPI performance in --test mode.
> >
> > Notes:
> >   o  benchmark computes results by summing cracks across all nodes and
> > dividing that by the AVERAGE of the crack-times. (in the code, cracks
> are
> > multiplied by the MPI-size, which is the same thing).
> >
> > Known bugs:
> >   o   john.pot gets littered with extraneous output, usually low
> integers
> > like "4" or "1" and a newline. Very strange. Still trying to track it
> down.
> >   o   successfull cracks do not get posted to the other tasks
> >   o   use of external filter with internal checksum causes a slight
> (1-2%)
> > slowdown
> >
> >
> > Incorporate the john.conf file into yours (or the default)... then run
> with:
> >
> >  mpirun <mpirun-args> john <mode> --external=MPIbyInternalKeySum
> > --session=john%d.rec
> >
> > For a restore:
> >
> >  mpirun <mpirun-args> john --restore=john%d.rec
> >
> > You can also benchmark it:
> >
> > mpirun <mpirun-args> john --test
> >
> >
> > --
> > Otheus
> > otheus@...il.com
> > +43.650.790.2571
> > --
> > To unsubscribe, e-mail
> > john-users-unsubscribe@...ts.openwall.com and reply
> > to the automated confirmation request that will be sent to you.
> >
> >
>
> --
> To unsubscribe, e-mail john-users-unsubscribe@...ts.openwall.com and reply
> to the automated confirmation request that will be sent to you.
>
>


-- 
Otheus
otheus@...il.com
+43.650.790.2571

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.