I've submitted a patch to fix the Torque launch issue - just some leftover
garbage that existed at the time of the 1.7.0 branch and didn't get removed.
For the hostfile issue, I'm stumped as I can't see how the problem would come
about. Could you please rerun your original test and add "--displa
Simple to do - I added a clearer error message to the trunk and marked it for
inclusion in the eventual v1.7.1 release. I'll have to let someone else do the
docs as I don't fully grok the rationale behind it.
Thanks
On Mar 18, 2013, at 12:56 PM, Jeremiah Willcock wrote:
> If a user gives an i
Hi,
1) Openmpi in PC1
I installed openmpi-1.4.3 using the OpenSuse 32b v. 12.1 repository
as well as openmpi devel
All mpi executables are present so are the libraries in lib directory.
I set the environment as ( .bashrc)
PATH=$PATH:/usr/lib/mpi/gcc/openmpi/bin
PATH=$PATH:/usr/lib/mpi/gcc/o
Well, a couple of things come to mind - see below
On Mar 20, 2013, at 9:41 AM, Bruno Cramer wrote:
> Hi,
> 1) Openmpi in PC1
> I installed openmpi-1.4.3 using the OpenSuse 32b v. 12.1 repository
> as well as openmpi devel
> All mpi executables are present so are the libraries in lib directory.
Am 20.03.2013 um 18:58 schrieb Ralph Castain:
> Well, a couple of things come to mind - see below
>
> On Mar 20, 2013, at 9:41 AM, Bruno Cramer wrote:
>
>> Hi,
>> 1) Openmpi in PC1
>> I installed openmpi-1.4.3 using the OpenSuse 32b v. 12.1 repository
>> as well as openmpi devel
>> All mpi ex
Hello ,
I am running NAS parallel benchmark's BTIO benchmark (NPB v 3.3) for class
D and 1 process.
`make bt CLASS=D SUBTYPE=full NPROCS=1`
I have provided gcc's `mcmodel=medium` flag alongwith -O3 during
compilation. This is on an x86_64 machine.
I have tested with openmpi 1.4.3, 1.7, but I ge
Hi Ralph,
Here is a result of rerun with --display-allocation.
I set OMP_NUM_THREADS=1 to make the problem clear.
Regards,
Tetsuya Mishima
P.S. As far as I checked, these 2 cases are OK(no problem).
(1)mpirun -v -np $NPROCS-x OMP_NUM_THREADS --display-allocation
~/Ducom/testbed/mPre m02-ld
(2)
You obviously have some MCA params set somewhere:
> --
> A deprecated MCA parameter value was specified in an MCA parameter
> file. Deprecated MCA parameters should be avoided; they may disappear
> in future releases.
>
> D
Could you please apply the attached patch and try it again? If you haven't had
time to configure with --enable-debug, that is fine - this will output
regardless.
Thanks
Ralph
user.diff
Description: Binary data
On Mar 20, 2013, at 4:59 PM, Ralph Castain wrote:
> You obviously have some MCA
Hi Ralph,
I have a line below in ~/.openmpi/mca-params.conf to use rsh.
orte_rsh_agent = /usr/bin/rsh
I changed this line to:
plm_rsh_agent = /usr/bin/rsh # for openmpi-1.7
Then, the error message disappeared. Thanks.
Retruning to the subject, I can rebuild with --enable-debug.
Just wait unt
Hi Ralph,
I have completed rebuild of openmpi1.7rc8.
To save time, I added --disable-vt. ( Is it OK? )
Well, what shall I do ?
./configure \
--prefix=/home/mishima/opt/mpi/openmpi-1.7rc8-pgi12.9 \
--with-tm \
--with-verbs \
--disable-ipv6 \
--disable-vt \
--enable-debug \
CC=pgcc CFLAGS="-fast
Hi Ralph,
Here is an output on openmpi-1.6.4, just for your information.
Small difference is obserbed. I hope this helps you.
Regards,
Tetusya Mishima
openmpi-1.6.4:
== ALLOCATED NODES ==
Data for node: node06.cluster Num slots: 4Max slots: 0
12 matches
Mail list logo
