In the usual place:
http://www.open-mpi.org/software/ompi/v1.5/
Please test! I would really like to get this out by the end of the week.
Two issues *might* still be considered for this release:
Putting back the openib minor fixes
https://svn.open-mpi.org/trac/ompi/ticket/2930
I noticed today a drastic change in how ORTE deal with the hostfile between
trunk and 1.5.
1. 1.5 and prior used the hostile as a suggestion, a placeholder where to pick
the requested number of daemons during the launch. The current trunk spawn
daemons on all the nodes provided on the host file
While I no longer have working Quadrics h/w, I still have the s/w
installed on 2 Linux hosts.
Both the of the following were configured with only a --prefix argument
and "make all install check" ran w/o incident:
System 1: Linux/x86-64
$ cat /etc/redhat-release
CentOS release 4.2 (Final)
$ una
I have tried 8 non-mainstream test platforms, using their "/usr/bin/gcc"
compilers:
MacOS 10.3 (Panther) on PPC:
gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1666)
MacOS 10.4 (Tiger) on PPC:
powerpc-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc.
build 5341)
MacOS 10.5 (L
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/12/11 12:59, Jeff Squyres wrote:
> Fair enough. We've definitely seen cases where the
> /tmp filesystem *did* matter, so perhaps it's a kernel
> version issue, or a phase of the moon issue, or...
Well it's more where $TMPDIR points to, not rel
Dear All,
I fixed the patch.
(MPI::Fint etc.)
So, please replace the patch.
Best regards.
---
Yuki MATSUMOTO
MPI development team,
Fujitsu
(2011/12/09 11:35), Y.MATSUMOTO wrote:
Dear Jeff and all,
Thank you for your comment.
I'm sorry for not replying sooner.
1:MPI::Fint
We chec
On Dec 13, 2011, at 5:56 PM, Christopher Samuel wrote:
>> Did David's suggestion help?
>
> It did, thanks - though I take David's point that there doesn't seem to
> be any measurable difference between using local storage (or even tmpfs)
> and Lustre for this so it seems like a warning that shoul
On Dec 13, 2011, at 7:59 PM, Christopher Yeoh wrote:
> Sorry, late to the discussion. This is a spurious warning caused by
> passing the NULL pointer to the opal free function which is actually ok.
> It was fixed by #2884 - this is why you don't see the problem in trunk.
I have a dim recollection
Hi Mike,
On Mon, 12 Dec 2011 19:46:08 +0200
Mike Dubman wrote:
> Hi guys,
>
> The latest v1.5 from trunk, compiled in debug mode yields following
> error with openib.
> The quick blame leads to the following commit:
>
> r25616 | bosilca | 2011-12-10 00:18:16 +0200 (Sat, 10 Dec 2011) | 4
> line
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/12/11 07:44, David Singleton wrote:
> This is why I was hoping sites could be given the opportunity to control
> that warning message.
Just to confirm that I see negligible difference between Panasas, local
SATA drives and /dev/shm memory backe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/12/11 07:44, David Singleton wrote:
> Hi Chris,
Hello David!
> Try setting OMPI_MCA_orte_tmpdir_base.
That works, thanks!
> Going back to a related earlier OMPI users thread ("How to set up
> state-less node /tmp for OpenMPI usage"), here ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/12/11 09:21, Jeff Squyres wrote:
> On Dec 13, 2011, at 1:10 AM, Christopher Samuel wrote:
>
> > I think you want s/settings/setting/ there.
>
> Fixed! Thanks.
Not a problem.
> > Also I can not seem to make it accept the orte_no_session_dir
>
On Dec 13, 2011, at 1:10 AM, Christopher Samuel wrote:
> It now complains that $TMPDIR points to our Panasas filesystem,
> and there's a minor typo in its message, saying:
>
> # Note, too, that system administrators can set a list of filesystems
> # where Open MPI is disallowed from creating tem
Hi Chris,
Try setting OMPI_MCA_orte_tmpdir_base.
Going back to a related earlier OMPI users thread ("How to set up state-less node /tmp for OpenMPI usage"), here are sm pingpong latencies (using 1.4.3) for
session dirs on Lustre, an SSD and tmpfs:
[dbs900@v1490 ~/MPI]$ export OMPI_MCA_orte_t
We decided on the call to just roll this back for 1.5.5, and fully
investigate/fix for 1.6.
On Dec 13, 2011, at 3:10 PM, Mike Dubman wrote:
> btw, it appears, that problem happens when CFLAGS="-g -O0" during configure
> phase.
> another clone compiled w/o this option did not cry.
>
> On Tue,
btw, it appears, that problem happens when CFLAGS="-g -O0" during configure
phase.
another clone compiled w/o this option did not cry.
On Tue, Dec 13, 2011 at 6:10 PM, George Bosilca wrote:
> We are investigating. A fix will be hopefully provided soon.
>
> Thanks for the report,
> george.
>
>
It's gone. No worries.
On Dec 13, 2011, at 1:46 PM, Hjelm, Nathan T wrote:
> I don't know how load_balance got into my tree. I have tried several times to
> remove it and didn't see it in the commit message (looks like it was a single
> line). I can blow it away if it hasn't already been remo
I don't know how load_balance got into my tree. I have tried several times to
remove it and didn't see it in the commit message (looks like it was a single
line). I can blow it away if it hasn't already been removed.
-Nathan
From: Ralph Castain [rhc.open
We are investigating. A fix will be hopefully provided soon.
Thanks for the report,
george.
On Dec 13, 2011, at 00:25 , Mike Dubman wrote:
> nope
>
> On Mon, Dec 12, 2011 at 10:40 PM, George Bosilca wrote:
> Do we have the same issue in the trunk?
>
> george.
>
> On Dec 12, 2011, at 12:4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/12/11 09:13, Jeff Squyres wrote:
> Gearing up for a pre-Christmas release -- please test!
Had a quick test here (we're still on 1.4.2 as our default).
It now complains that $TMPDIR points to our Panasas filesystem,
and there's a minor typo in
nope
On Mon, Dec 12, 2011 at 10:40 PM, George Bosilca wrote:
> Do we have the same issue in the trunk?
>
> george.
>
> On Dec 12, 2011, at 12:49 , Mike Dubman wrote:
>
> after removing my debug prints - the correct line is 448
>
> On Mon, Dec 12, 2011 at 7:46 PM, Mike Dubman wrote:
>
>>
>>
21 matches
Mail list logo
