[openfabrics-ewg] [openib-general] MVAPICH2 SRPM and install file patches

[Scott Weitzenkamp (sweitzen)]

Shaun,

Thanks for doing this.

I see things like romio and shlibs configurable in the patch, what about
other MVAPICH2 features like fault tolerance, multi rail, threads, and
MPD?  How can configure them when I use install.sh to compile and
install OFED?

I also didn't quite understand the ib-vs-iwarp configuration, I thought
OFED 1.2 would support both.

Scott Weitzenkamp
SQA and Release Manager
Server Virtualization Business Unit
Cisco Systems
 

> -----Original Message-----
> From: openib-general-bounces at openib.org 
> [mailto:openib-general-bounces at openib.org] On Behalf Of Shaun Rowland
> Sent: Wednesday, January 31, 2007 5:33 PM
> To: vlad at dev.mellanox.co.il
> Cc: openfabrics-ewg at openib.org; openib-general at openib.org
> Subject: [openib-general] MVAPICH2 SRPM and install file patches
> 
> I've placed the MVAPICH2 SRPM on the OFA server in ~rowland/ofed_1_2,
> and it is linked to here:
> 
> http://www.openfabrics.org/~rowland/ofed_1_2/
> 
> Additionally, I am including a patch in this email that updates the
> ofed_1_2_scripts files from the GIT repository we were given to
> handle the MVAPICH2 SRPM file. Basically, installing MVAPICH2 
> is similar
> to the other MPI packages, except that I have added a choice option to
> build with iWARP support or not. The default is IB only. If 
> the user has
> selected the librdmacm packages and the mvapich2 package, 
> this choice is
> presented. This is also saved in the ofed.conf file using an
> MVAPICH2_IMPL variable, and the librdmacm packages are added as
> dependencies if the iWARP version of MVAPICH2 is desired and they are
> not already in the ofed.conf file, which seems like standard 
> behavior in
> the scripts. The resulting binary RPM uses the name convention
> mvapich2_<compiler> as normal in either case. There are various ways
> this could be implemented, perhaps in a better manner. This is what I
> was able to come up with by today. Since the installation 
> scripts given
> were very similar to the original OFED 1.1 scripts, I was able to test
> the installation procedure using OFED 1.1 files. Everything worked for
> me, including building the mpitests package against the mvapich2
> package. There are some comments about this in what I have 
> done. I hope
> that it is helpful in getting our SRPM integrated into the 
> installation
> scripts.
> 
> Additionally, I put a README file in my ofed_1_2 directory 
> that contains
> information about the macros that can be used with our SRPM file. The
> SRPM can be used to install against an existing OFED installation, and
> those macros control various aspects of the result. There is 
> one special
> macro I use for when the SRPM is being built along with the 
> OFED source,
> and its use should be clear in the patched build.sh script and
> associated comment.
> -- 
> Shaun Rowland	rowland at cse.ohio-state.edu
> http://www.cse.ohio-state.edu/~rowland/
>