Jeff,
I believe that with quicktime-pro you can export the videos in
several formats.
Doug Reeder
On Jun 3, 2008, at 1:48 PM, Jeff Squyres wrote:
On May 30, 2008, at 9:55 AM, Andreas Schäfer wrote:
I've never really dig into Open MPI's guts, not because I wasn't
interested, but mainly bec
Note that "eager" RDMA is only used for short messages -- it's not
really relevant to whether the same user buffers are re-used or not
(the mpi_leave_pinned parameter for long messages is only useful if
long buffers are re-used). See this FAQ item:
http://www.open-mpi.org/faq/?category=ope
Excellent point; thanks for the heads-up!
I've updated the SLURM docs in the FAQ accordingly.
On Jun 5, 2008, at 6:15 PM, Bill Johnstone wrote:
Hello all.
It would seem that the documentation, at least the FAQ page at http://www.open-mpi.org/faq/?category=slurm
is a little out of date with
Hello all.
It would seem that the documentation, at least the FAQ page at
http://www.open-mpi.org/faq/?category=slurm is a little out of date with
respect to running on newer versions of SLURM (I just got things working with
version 1.3.3) .
According to the SLURM documentation, srun -A is dep
On Jun 5, 2008, at 9:21 AM, Jeff Squyres wrote:
On Jun 4, 2008, at 4:28 PM, Brock Palen wrote:
We have two installs of openmpi-1.2.3
One with the pgi compilers the other with gcc/Nagf90
One the pgi compilers does not link against libibverbs, but ompi_info
shows the openib btl and we see traffi
Hi,
i'm testing SKaMPI Benchmark on IBM Blade System over Infiniband. Current
version of OpenMPI is 1.2.6
I have tried to disable RDMA setting btl_openib_use_eager_rdma = 0. But, i
have noted that, in MPI collectives execution time, there are few difference
beetween RDMA active and none. Before tes
On Jun 4, 2008, at 4:28 PM, Brock Palen wrote:
We have two installs of openmpi-1.2.3
One with the pgi compilers the other with gcc/Nagf90
One the pgi compilers does not link against libibverbs, but ompi_info
shows the openib btl and we see traffic on the fabric.
The other built with Nagware li
Hi Jeff,
This suggests that perhaps 1.2.6 was configured with --enable-static
or --disable-dlopen. If either of these two options were used, OMPI
will suck all the plugins to become part of libmpi (and friends), and
therefore the plugins' dependencies will therefore become dependencies
o
On Jun 5, 2008, at 7:56 AM, Samuel Sarholz wrote:
Nothing changed between 1.2.5 and 1.2.6 with regards to depending
on libibverbs.
Ok then I need to check what we did differently when installing both
versions.
The mpicc wrapper from 1.2.6 links -libverbs.
(It shows up with mpicc -V).
T
Hi,
Nothing changed between 1.2.5 and 1.2.6 with regards to depending on
libibverbs.
Ok then I need to check what we did differently when installing both
versions.
The mpicc wrapper from 1.2.6 links -libverbs.
(It shows up with mpicc -V).
Does ldd show that your apps depend on libibver
On Jun 5, 2008, at 4:37 AM, Samuel Sarholz wrote:
we have a some issues with the openmpi 1.2.6 and libibverbs.
We have some machines with Infiniband and some without.
We compiled openmpi with IB support.
With OpenMPI 1.2.5 it was no problem running that version on the
machines without IB.
How
You can translate the communicator from Fortran to C using the MPI_COMM_F2C
routine.
--td
Message: 4
Date: Thu, 05 Jun 2008 08:53:55 +0200
From: Samuel Sarholz
Subject: [OMPI users] Communicators in Fortran and C
To: us...@open-mpi.org
Message-ID: <48478d83.6080...@rz.rwth-aachen.de>
Content-T
If I correctly understand how you run your application I think I know
where the problem is coming from. In few words you're using buffered
send over shared memory.
First, buffered send has only one main benefit, it double the amount
of memory required for the communication. A side effect is
Hi,
we have a some issues with the openmpi 1.2.6 and libibverbs.
We have some machines with Infiniband and some without.
We compiled openmpi with IB support.
With OpenMPI 1.2.5 it was no problem running that version on the
machines without IB.
However with 1.2.6 the library libibverbs is linked
Hi,
I have problems running a Fortran program which is calling a C library
with OpenMPI.
The problem is that the Fortan part has a communicator which is passed
to the C library.
And if I understand the headers right a communicator is an integer in
fortran, but a struct on the C side of openm
15 matches
Mail list logo
