Re: [MTT users] funclet and quoting

On Tue, Jun/12/2007 04:53:21PM, Jeff Squyres wrote: > On Jun 12, 2007, at 10:50 AM, Ethan Mallove wrote: > > >>> eval $btls = MTT::Functions::if(MTT::Functions::regexp > >>> (MTT::Functions::shell("hostname"), "v440-2|v20z-2"), > >>> MTT::Functions::enumerate("self,sm,tcp"), >

Re: [MTT users] funclet and quoting

On Jun 12, 2007, at 10:50 AM, Ethan Mallove wrote: eval $btls = MTT::Functions::if(MTT::Functions::regexp (MTT::Functions::shell("hostname"), "v440-2|v20z-2"), MTT::Functions::enumerate("self,sm,tcp"), MTT::Functions::if("MTT::Functions::regexp

Re: [OMPI users] TCP connection errors

On 12/06/07, George Bosilca wrote: Jonathan Underwood wrote: > Presumably switching the two interfaces on the frontend (eth0<->eth1) > would also solve this problem? > If you have root privileges this seems to be a another good approach. I don't, but will explain the issue

Re: [OMPI users] TCP connection errors

Jonathan Underwood wrote: Presumably switching the two interfaces on the frontend (eth0<->eth1) would also solve this problem? If you have root privileges this seems to be a another good approach. george.

Re: [OMPI users] TCP connection errors

On 12/06/07, George Bosilca wrote: Jonathan, It will be difficult to make it works in this configuration. The problem is that on the head node the network interface that have to be used is eth1 while on the compute nodes is eth0. Therefore, the tcp_if_include will not help

Re: [OMPI users] f90 support not built with gfortran?

Thanks guys! Setting F77=gfortran did the trick. Jeff F. Pummill Senior Linux Cluster Administrator University of Arkansas Fayetteville, Arkansas 72701 (479) 575 - 4590 http://hpc.uark.edu "A supercomputer is a device for turning compute-bound problems into I/O-bound problems." -Seymour Cray

Re: [OMPI users] rdma over tcp?

On Jun 12, 2007, at 10:52 AM, Brian Barrett wrote: On Jun 11, 2007, at 9:27 AM, Brock Palen wrote: With openmpi-1.2.0 i ran a: ompi_info --param btl tcp and i see reference to: MCA btl: parameter "btl_tcp_min_rdma_size" (current value: "131072") MCA btl: parameter "btl_tcp_max_rdma_size"

Re: [MTT users] funclet and quoting

On Tue, Jun/12/2007 08:07:20AM, Jeff Squyres wrote: > On Jun 11, 2007, at 6:02 PM, Ethan Mallove wrote: > > > btls = ("("("hostname")", "v440-2|v20z-2")", \ > >"("self,sm,tcp")", \ > >"("("("hostname")", "v440-6")", \ > >"("udapl")", \ > >

Re: [OMPI users] mpirun hanging when processes started on head node

Hi Sean > [Sean] I'm working through the strace output to follow the progression on the > head node. It looks like mpirun consults '/bpfs/self' and determines that the > request is to be run on the local machine so it fork/execs 'orted' which then > runs 'hostname'. 'mpirun' didn't consult

Re: [MTT users] funclet and quoting

On Jun 11, 2007, at 6:02 PM, Ethan Mallove wrote: btls = ("("("hostname")", "v440-2|v20z-2")", \ "("self,sm,tcp")", \ "("("("hostname")", "v440-6")", \ "("udapl")", \ "("sm", "tcp", "sm,tcp", "udapl", "sm,udapl")"" \ ) \ )

Re: [OMPI users] f90 support not built with gfortran?

On Jun 12, 2007, at 5:56 AM, Terry Frankcombe wrote: I downloaded and configured v1.2.2 this morning on an Opteron cluster using the following configure directives... ./configure --prefix=/share/apps CC=gcc CXX=g++ F77=g77 FC=gfortran CFLAGS=-m64 CXXFLAGS=-m64 FFLAGS=-m64 FCFLAGS=-m64 What

Re: [OMPI users] f90 support not built with gfortran?

On Mon, 2007-06-11 at 12:10 -0500, Jeff Pummill wrote: > Greetings all, > > I downloaded and configured v1.2.2 this morning on an Opteron cluster > using the following configure directives... > > ./configure --prefix=/share/apps CC=gcc CXX=g++ F77=g77 FC=gfortran > CFLAGS=-m64 CXXFLAGS=-m64

Re: [OMPI users] TCP connection errors

Jonathan, It will be difficult to make it works in this configuration. The problem is that on the head node the network interface that have to be used is eth1 while on the compute nodes is eth0. Therefore, the tcp_if_include will not help ... Now, if you only start processes on the compute

Re: [OMPI users] mixing MX and TCP

Well, as expected this call is not documented ... and I get to it only with some help from Loic. On the version of MX I have tested it is not required to add the 3th and 4th arguments as I don't want to set anything. The NIC is already specified through the mx_btl->mx_endpoint isn't it ?