All organizations should review the README file (particularly the
list of supported systems, etc.) to ensure that it is good-to-go and
accurate for the 1.2.4. release.
Tim posted 1.2.4rc1 yesterday:
http://www.open-mpi.org/software/ompi/v1.2/
--
Jeff Squyres
Cisco Systems
Jeff Squyres wrote:
All organizations should review the README file (particularly the
list of supported systems, etc.) to ensure that it is good-to-go and
accurate for the 1.2.4. release.
Tim posted 1.2.4rc1 yesterday:
http://www.open-mpi.org/software/ompi/v1.2/
I would like to req
No issues from Cisco. If an optimized build was not used, that could
well account for the discrepancy.
On Sep 19, 2007, at 9:18 AM, Terry Dontje wrote:
Jeff Squyres wrote:
All organizations should review the README file (particularly the
list of supported systems, etc.) to ensure that it i
In doing some runs with the osu_bibw test on a single node, we have
found that it hands when using the trunk for message sizes 2097152 or
larger unless the mpool_sm_min_size is set to a number larger than the
message size. We are not seeing this issue in the 1.2 branch. Just
checking to see i
On Wed, Sep 19, 2007 at 10:26:15AM -0400, Dan Lacher wrote:
> In doing some runs with the osu_bibw test on a single node, we have
> found that it hands when using the trunk for message sizes 2097152 or
> larger unless the mpool_sm_min_size is set to a number larger than the
> message size. We a
Hi,
Just to verify, before I'll start testing this, there will be no message
queue debugging support in this version, correct? This all goes to 1.3 release.
Best Regards,
P.S. It looks like it is time for us to be more formally involved in this work.
Nikolay Piskun
Director of Continuing
Hi. I have been trying to build the latest ompi-trunk (as of yesterday)
svn snapshot (r16158) of OpenMPI on a FreeBSD 6.2 machine and have run
into 3 build problems. I was curious if anyone else has encountered
these errors and if they are being addressed.
Problem 1
-
When running the auto
Nikolay and Community,
Sorry to be so late in responding to your email but I've been working
with Pak to determine whether my hasty decision as RM yesterday was
hasty or not. To answer your question, we are still trying to determine
if the message queue support can go in or not and the below
This all sounds reasonable to me. I agree -- now that the dramatic
performance difference has been explained and we're within a tiny
delta (that's likely simply the normal testing variance), let's put
the MQ stuff in 1.2.4.
(BTW, I didn't surmise that Pak had debugging enabled; I think he
Terry,
Are the performance numbers still with debugging turned on ? The sm latency
(trunk and tmp) is about 2.5 x higher than I typically see. BTW, if the tmp
branch is running coming in essentially the same, looks like there is no
performance problem with the changes.
Rich
- Origina
Rich,
Yes. Both my tmp branch and 1.2 branch are both configured with -g. The
--enable-debug flag was taken out for my tmp branch previously, that
should explain the latency last time.
Graham, Richard L. wrote:
Terry,
Are the performance numbers still with debugging turned on ? The sm la
Hi Karol,
Thanks for the reports.
I cannot help with the first problem. Maybe someone else can.
Problem 2: I have committed your suggested fix in r16163.
As for the third problem, this is very strange. It looks like what is
happening is that we are in the ompi/mpi/f77 directory compiling a .c
Hi, Tim. Thanks for the reply.
v1.2.3 and v1.2.4rc1 were both compiled, without problems, from tarballs.
Tim Prins wrote:
> Hi Karol,
>
> Thanks for the reports.
>
> I cannot help with the first problem. Maybe someone else can.
>
> Problem 2: I have committed your suggested fix in r16163.
>
>
On Sep 19, 2007, at 4:11 PM, Tim Prins wrote:
Here is where it gets nasty. On FreeBSD, /usr/include/string.h
includes
strings.h in some cases. But there is a strings.h in the ompi/mpi/f77
directory, so that is getting included instead of the proper
/usr/include/strings.h.
I suppose we could r
This is fixed in r16164.
Tim
Brian Barrett wrote:
On Sep 19, 2007, at 4:11 PM, Tim Prins wrote:
Here is where it gets nasty. On FreeBSD, /usr/include/string.h
includes
strings.h in some cases. But there is a strings.h in the ompi/mpi/f77
directory, so that is getting included instead of the
15 matches
Mail list logo
