On Fri, 11 Jun 2004, Richard Hadsell wrote:
> I think it would be helpful for laminfo to supply a bit more information
> about the configuration. I would like to see whether the LAM tools were
> built with or without exception throwing from the functions and with or
> without thread support. There are probably a few other options that
> would be useful to know when trying to figure out why your application
> isn't behaving the way you expected. If the list gets to be too long,
> it could be controlled with command-line options.
Excellent suggestions; thanks!
Sidenote: I love the laminfo command. I love it even more when people
find it useful! :-)
The laminfo command has been greatly augmented for 7.1; it already
includes both of these suggestions and also includes the capability to
print out all SSI parameters and their default values. Here's what the
output of 7.1's laminfo looks like (this is the prettyprint version; the
"-parsable" is also available, of course):
-----
[11:37] queeg:~ % laminfo
LAM/MPI: 7.1a1svn
Prefix: /home/jsquyres/local
Architecture: i686-pc-linux-gnu
Configured by: jsquyres
Configured on: Wed Jun 2 08:42:48 EDT 2004
Configure host: build.lam-mpi.org
C bindings: yes
C++ bindings: no
Fortran bindings: no
C compiler: gcc
C++ compiler: g++
Fortran compiler: false
Fortran symbols: none
C profiling: no
C++ profiling: no
Fortran profiling: no
C++ exceptions: no
Thread support: yes
ROMIO support: no
IMPI support: no
Debug support: yes
Purify clean: yes
SSI boot: globus (API v1.1, Module v0.5)
SSI boot: rsh (API v1.1, Module v1.0)
SSI boot: slurm (API v1.1, Module v1.0)
SSI coll: lam_basic (API v1.1, Module v7.1)
SSI coll: shmem (API v1.1, Module v1.0)
SSI coll: smp (API v1.1, Module v1.1)
SSI rpi: crtcp (API v1.1, Module v1.0.1)
SSI rpi: lamd (API v1.0, Module v7.0)
SSI rpi: sysv (API v1.0, Module v7.0)
SSI rpi: tcp (API v1.0, Module v7.0)
SSI rpi: usysv (API v1.0, Module v7.0)
-----
The "-param" option is used to show SSI params. It takes 2 arguments: the
SSI type and the SSI module name. The special name "all" is a wildcard.
This example displays all types and all modules (-parsable is also
availabe here, too, of course):
-----
[11:38] queeg:~ % laminfo -param all all
SSI base: parameter "verbose" (default value: <none>)
SSI mpi: parameter "mpi_hostmap" (default value:
"/home/jsquyres/local/etc/lam-hostmap.txt")
SSI base: parameter "base_module_path" (default value:
"/home/jsquyres/local/lib/lam")
SSI boot: parameter "boot_verbose" (default value: <none>)
SSI boot: parameter "boot" (default value: <none>)
SSI boot: parameter "boot_base_promisc" (default value: "0")
SSI boot: parameter "boot_base_window_size" (default value: "5")
SSI boot: parameter "boot_globus_priority" (default value: "3")
SSI boot: parameter "boot_rsh_username" (default value: <none>)
SSI boot: parameter "boot_rsh_agent" (default value: "ssh")
SSI boot: parameter "boot_rsh_no_n" (default value: "0")
SSI boot: parameter "boot_rsh_no_profile" (default value: "0")
SSI boot: parameter "boot_rsh_fast" (default value: "0")
SSI boot: parameter "boot_rsh_ignore_stderr" (default value: "0")
SSI boot: parameter "boot_rsh_priority" (default value: "10")
SSI boot: parameter "boot_slurm_priority" (default value: "50")
SSI rpi: parameter "rpi_verbose" (default value: <none>)
SSI rpi: parameter "rpi" (default value: <none>)
SSI rpi: parameter "rpi_crtcp_priority" (default value: "25")
SSI rpi: parameter "rpi_crtcp_short" (default value: "65536")
SSI rpi: parameter "rpi_crtcp_sockbuf" (default value: "-1")
SSI rpi: parameter "rpi_lamd_priority" (default value: "20")
SSI rpi: parameter "rpi_sysv_pollyield" (default value: "1")
SSI rpi: parameter "rpi_sysv_poolsize" (default value:
"16777216")
SSI rpi: parameter "rpi_sysv_maxalloc" (default value:
"1048576")
SSI rpi: parameter "rpi_sysv_short" (default value: "8192")
SSI rpi: parameter "rpi_tcp_short" (default value: "65536")
SSI rpi: parameter "rpi_tcp_sockbuf" (default value: "-1")
SSI rpi: parameter "rpi_sysv_priority" (default value: "30")
SSI rpi: parameter "rpi_tcp_priority" (default value: "20")
SSI rpi: parameter "rpi_usysv_readlockpoll" (default value:
"10000")
SSI rpi: parameter "rpi_usysv_writelockpoll" (default value:
"10")
SSI rpi: parameter "rpi_usysv_pollyield" (default value: "1")
SSI rpi: parameter "rpi_usysv_poolsize" (default value:
"16777216")
SSI rpi: parameter "rpi_usysv_maxalloc" (default value:
"1048576")
SSI rpi: parameter "rpi_usysv_short" (default value: "8192")
SSI rpi: parameter "rpi_usysv_priority" (default value: "40")
SSI coll: parameter "coll_verbose" (default value: <none>)
SSI cr: parameter "cr_verbose" (default value: <none>)
SSI cr: parameter "cr" (default value: <none>)
-----
>From these parameters, a discerning LAM user will notice a few features
(some of which have been mentioned on this list, some of which have not),
such as a SLURM boot module, the ability to ignore stderr in the rsh boot
module, etc.
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
