Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Hardware Locality Development mailing list

Subject: Re: [hwloc-devel] Crash with ignoring HWLOC_OBJ_NODE in 0.9.2
From: Michael Raymond (mraymond_at_[hidden])
Date: 2009-11-30 10:56:23

  Software modules, eg on SuSE see the Modules RPM. The way that a lot
of software installations used to be managed was to throw them all under
/usr in the standard directories. This kept library paths and include
in default places but breaks down when you have multiple installations
of a product, conflicting names, want to keep installations on central
file servers, etc. Modules let you install the package wherever is
convenient and then easy load the environment when you actually want the

  For example:

module load intel-compilers-11
module load mpt/1.25
<compile and test>

module unload mpt/1.25 intel-compilers-11
module load intel-compilers-9
module load mpt/1.22
module load totalview
<compile and test>

  This easily lets me modify which versions of the various products I'm
using. The `module load` command modifies my shell's LD_LIBRARY_PATH,
LD_PATH, PATH, MANPATH, MPIROOT, CPATH, etc variables. For hwloc I could:

module load hwloc

  This keeps hwloc out of /usr thus keeping the Linux File Hierarchy
Standard (LFHS) happy.

Samuel Thibault wrote:
> Michael Raymond, le Mon 30 Nov 2009 09:23:02 -0600, a écrit :
>> At the moment I'm thinking SLES11 (and RHEL6) RPMs of 0.9.3 / TOT
>> installed in /opt[/sgi]/hwloc. I'd also add module support.
> What do you mean by "module support"?
> Samuel
> _______________________________________________
> hwloc-devel mailing list
> hwloc-devel_at_[hidden]

Michael A. Raymond
Message Passing Toolkit Team
Silicon Graphics Inc
(651) 683-3434