NAME

       likwid-mpirun - A tool to start and monitor MPI applications with LIKWID

SYNOPSIS

       likwid-memsweeper  [-hd]  [-hostfile filename] [-nperdomain number_of_processes_in_domain]
       [-pin expression] [-omp expression] [-mpi expression] [--]

DESCRIPTION

       likwid-mpirun is a command line application that wraps the vendor-specific mpirun tool and
       adds  calls  to  likwid-perfctr(1)  to the execution string. The user-given application is
       ran, measured and the results returned to the staring node.

OPTIONS

       -h     prints a help message to standard output, then exits.

       -d     prints debug messages to standard output.

       -hostfile  filename
              specifies the nodes to schedule the MPI processes on

       -nperdomain  number_of_processes_in_domain
              specifies the processes per affinity domain (see likwid-pin for info about affinity
              domains)

       -pin  expression
              specifies  the pinning for hybrid execution (see likwid-pin for info about affinity
              domains)

       -omp  expression
              enables hybrid setup. Can only be used in combination with -pin.  The only possible
              value is: intel

       -mpi  expression
              specifies  the  MPI  implementation  that  should  be used by the wrapper. Possible
              values are intelmpi, openmpi and mvapich2

       --     stops parsing arguments for likwid-mpirun, in order to set options  for  underlying
              MPI implementation after --.

EXAMPLE

       1.  For standard application:

       likwid-mpirun -np 32 ./myApp

       Will run 32 MPI processes, each host is filled with as much processes as written in ppn

       2.  With pinning:

       likwid-mpirun -np 32 -nperdomain S:2 ./myApp

       Will start 32 MPI processes with 2 processes per socket.

       3.  For hybrid runs:

       likwid-mpirun -np 32 -pin M0:0-3_M1:0-3 ./myApp

       Will  start  32  MPI processes with 2 processes per node. Threads of the first process are
       pinned to the cores 0-3 in NUMA domain 0 (M0). The OpenMP threads of  the  second  process
       are pinned to the first four cores in NUMA domain 1 (M1)

AUTHOR

       Written by Thomas Roehl <thomas.roehl@gmail.com>.

BUGS

       Report Bugs on <http://code.google.com/p/likwid/issues/list>.

SEE ALSO

       likwid-pin(1),   likwid-perfctr(1),   likwid-features(1),   likwid-powermeter(1),  likwid-
       topology(1),