On 7/11/07, George Bosilca wrote:
The two errors you provide are quite different. The first one has
been addresses few days ago in the trunk (https://svn.open-mpi.org/
trac/ompi/changeset/15291). If instead of the 1.2.3 you use anything
after r15291 you will be safe in a threading case.
Please
Lisandro,
The two errors you provide are quite different. The first one has
been addresses few days ago in the trunk (https://svn.open-mpi.org/
trac/ompi/changeset/15291). If instead of the 1.2.3 you use anything
after r15291 you will be safe in a threading case.
The second is different. T
Ups, sended to wrong list, forwarded here...
-- Forwarded message --
From: Lisandro Dalcin
List-Post: devel@lists.open-mpi.org
Date: Jul 11, 2007 8:58 PM
Subject: failures runing mpi4py testsuite, perhaps Comm.Split()
To: Open MPI
Hello all, after a long time I'm here again. I
Some supplementary information to the wiki at
https://svn.open-mpi.org/trac/ompi/wiki/CrayXT3.
I. Accessing the Open MPI source:
* Subversion is installed on redstorm in /projects/unsupported/bin
* Reddish has subversion in the default path (you don't have to load a
module)
* The proxy i
On Jul 11, 2007, at 8:09 AM, Terry D. Dontje wrote:
Jeff Squyres wrote:
On Jul 10, 2007, at 1:26 PM, Ralph H Castain wrote:
2. It may be useful to have some high-level parameters to specify a
specific run-time environment, since ORTE has multiple, related
frameworks (e.g., RAS and PLS).
Scott Atchley wrote:
On Jul 10, 2007, at 3:24 PM, Tim Prins wrote:
On Tuesday 10 July 2007 03:11:45 pm Scott Atchley wrote:
On Jul 10, 2007, at 2:58 PM, Scott Atchley wrote:
Tim, starting with the recently released 1.2.1, it is the default.
To clarify, MX_RCACHE=1 is the default.
It would b
On Wed, Jul 11, 2007 at 01:17:02PM +0200, Christoph Niethammer wrote:
> Hello,
>
>
> Since some time I'm testing Open MPI at the HRLS. My main topic there is the
> thread support of Open MPI.
>
> Some time ago I found a segmentation fault when running the svn-trunk
> Version.
> Thanks to the
Interesting point - no reason why we couldn't use that functionality for
this purpose. Good idea!
On 7/11/07 5:38 AM, "Jeff Squyres" wrote:
> On Jul 10, 2007, at 1:26 PM, Ralph H Castain wrote:
>
>>> 2. It may be useful to have some high-level parameters to specify a
>>> specific run-time envi
Jeff Squyres wrote:
On Jul 10, 2007, at 1:26 PM, Ralph H Castain wrote:
2. It may be useful to have some high-level parameters to specify a
specific run-time environment, since ORTE has multiple, related
frameworks (e.g., RAS and PLS). E.g., "orte_base_launcher=tm", or
somesuch.
I
On Jul 10, 2007, at 1:26 PM, Ralph H Castain wrote:
2. It may be useful to have some high-level parameters to specify a
specific run-time environment, since ORTE has multiple, related
frameworks (e.g., RAS and PLS). E.g., "orte_base_launcher=tm", or
somesuch.
I was just writing this up in an
Hello,
Since some time I'm testing Open MPI at the HRLS. My main topic there is the
thread support of Open MPI.
Some time ago I found a segmentation fault when running the svn-trunk Version.
Thanks to the help of Sven I could locate it now to be in the shared memory
btl. (ompi/mca/btl/sm/btl_
This is a bit off-topic for this list, but I was wondering if anyone
has any experience working with ptpd (precision time protocol daemon;
following the IEEE 1588 spec). The point of ptpd is to give better
time precision than NTP; NTP gives accuracy on the order of
miliseconds where ptpd/I
12 matches
Mail list logo
