Hi, Jeff
many thanks for your reply..
> 1. You might want to update your version of Open MPI if possible; the
> v1.1.1 version is quite old. We have added many new bug fixes and
> features since v1.1.1 (including tight SGE integration). There is
> nothing special about the Open MPI that i
Hi.
I think it is not necessary to specify the hosts via the hostfile using SGE
and OpenMPI, even the $NSLOTS is not necessary , just run
mpirun executable
this works very well.
to your memory problem:
I had similar problems when I specified the h_vmem option to use in SGE.
Without SGE everyt
Markus Daene schrieb:
> Hi.
>
> I think it is not necessary to specify the hosts via the hostfile using SGE
> and OpenMPI, even the $NSLOTS is not necessary , just run
> mpirun executable this works very well.
This produces the same error, but thanks for your suggestion. (For the
sake of intere
It couldn't be easier. Thanks a lot!
Pablo
On Friday 22 June 2007 00:32:13 George Bosilca wrote:
> Rerun the autogen.sh script and the new BTL will get auto-magically
> included in the build. You don't have to modify anything, just run
> the script.
>
> Once you get it compiled, you can speci
On Jun 22, 2007, at 3:52 AM, sad...@gmx.net wrote:
1. You might want to update your version of Open MPI if possible; the
v1.1.1 version is quite old. We have added many new bug fixes and
features since v1.1.1 (including tight SGE integration). There is
nothing special about the Open MPI that i
> Markus Daene wrote:
> > Hi.
> >
> > I think it is not necessary to specify the hosts via the hostfile using
> > SGE and OpenMPI, even the $NSLOTS is not necessary , just run
> > mpirun executable this works very well.
>
> This produces the same error, but thanks for your suggestion. (For the
> s
Markus Daene wrote:
>>> to your memory problem:
>>> I had similar problems when I specified the h_vmem option to use in SGE.
>>> Without SGE everything works, but starting with SGE gives such memory
>>> errors. You can easily check this with 'qconf -sc'. If you have used this
>>> option, try witho
Jeff Squyres wrote:
2. I know little/nothing about SGE, but I'm assuming that you need to
have SGE pass the proper memory lock limits to new processes. In an
interactive login, you showed that the max limit is "8162952" -- you
might just want to make it unlimited, unless you have a reason for
li
Hi Pak,
> Jeff Squyres wrote:
2. I know little/nothing about SGE, but I'm assuming that you need to
have SGE pass the proper memory lock limits to new processes. In an
interactive login, you showed that the max limit is "8162952" -- you
might just want to make it unlimited, un
Jeff Squyres schrieb:
>> Hmm, I've heard about conflicts with OMPI 1.2.x and OFED 1.1 (sorry no
>> refference here),
>
> I'm unaware of any problems with OMPI 1.2.x and OFED 1.1. I run OFED
> 1.1 on my cluster at Cisco and have many different versions of OMPI
> installed (1.2, trunk, etc.).
On Jun 22, 2007, at 10:44 AM, sad...@gmx.net wrote:
Can you send more information on this? See http://www.open-mpi.org/
community/help/
-sh-3.00$ ompi/bin/mpirun -d -np 2 -H node03,node06 hostname
[headnode:23178] connect_uni: connection not allowed
[headnode:23178] connect_uni: connection no
On Jun 20, 2007, at 8:29 AM, Jeff Squyres wrote:
1. btl_*_min_send_size is used to decide when to stop striping a
message across multiple BTL's. Is there a reason that we don't
just use eager_limit for this value? It seems weird to say "this
message is short enough to go across 1 BTL, eve
12 matches
Mail list logo
