Just for a change, I don't have a build problem!
However, I have a question about the MPI_Testsome() call. I'm using
MPI_Testsome() to check the completion status of a number of
outstanding ISend() requests. I'm doing something like this:
int outstanding;
main()
{
tids = (int *)malloc(
On Sep 16, 2005, at 2:17 PM, Ferris McCormick wrote:
On Fri, 2005-09-16 at 12:52 -0500, Brian Barrett wrote:
On Sep 16, 2005, at 11:35 AM, Brian Barrett wrote:
On Sep 16, 2005, at 8:44 AM, Ferris McCormick wrote:
==
fmccor@polylepis util [235]% ./opa
On Fri, 2005-09-16 at 12:52 -0500, Brian Barrett wrote:
> On Sep 16, 2005, at 11:35 AM, Brian Barrett wrote:
>
> > On Sep 16, 2005, at 8:44 AM, Ferris McCormick wrote:
> >
> >> ==
> >> fmccor@polylepis util [235]% ./opal_timer
> >> --> frequency: 9
>
On Sep 16, 2005, at 11:35 AM, Brian Barrett wrote:
On Sep 16, 2005, at 8:44 AM, Ferris McCormick wrote:
==
fmccor@polylepis util [235]% ./opal_timer
--> frequency: 9
--> cycle count
Slept approximately 903151189 cycles, or 1003501 us
--> usec
I concur -- I think that this test is meaningless and should be removed.
On Sep 16, 2005, at 12:41 PM, Brian Barrett wrote:
A quick question about MPI_Group_range_excl(). I notice that if for a
given triplet, first_rank == last_rank, we error if stride is not 1. I
notice we don't have that te
Hi all -
A quick question about MPI_Group_range_excl(). I notice that if for a
given triplet, first_rank == last_rank, we error if stride is not 1. I
notice we don't have that test in MPI_Group_range_incl(). Is there a
reason that test should be there - the standard doesn't seem to imply
t
On Sep 16, 2005, at 8:44 AM, Ferris McCormick wrote:
==
fmccor@polylepis util [235]% ./opal_timer
--> frequency: 9
--> cycle count
Slept approximately 903151189 cycles, or 1003501 us
--> usecs
Slept approximately 18446744073289684648 us
===
On Thu, 2005-09-15 at 20:25 -0500, Brian Barrett wrote:
> On Sep 15, 2005, at 8:17 PM, Ferris McCormick wrote:
>
> > On Thu, 15 Sep 2005, Ferris McCormick wrote:
> >
> >
> > A little experimentation suggests that instead of "mov %tick, ..." we
> > need
> > "rd %tick,%o4". I'll verify tomorrow w
Hi Jeff, Tim, James,
* Jeff Squyres wrote on Thu, Sep 15, 2005 at 02:55:26AM CEST:
>
> There appear to be two problems:
>
> - I borked up the libnuma configure.m4 such that mpicc (and friends)
> don't get the right flags for libnuma when you compile OMPI statically.
>
> - James' problem seems
