Ya -- that's part of the fixes for case 1.
I just committed that one fix -- assumedly that's enough for you for
the time being? (or do you want me to commit the rest of the fixes?)
Nothing calls this code yet, so if it compiles/links, you're fine.
On Aug 15, 2005, at 11:51 AM, Tim S. Wooda
There is a problem in the linux code:
[twoodall@roadkill linux]$ svn diff
Index: paffinity_linux_module.c
===
--- paffinity_linux_module.c(revision 6884)
+++ paffinity_linux_module.c(working copy)
@@ -162,7 +162,7 @@
We
Is anyone having problems compiling the "linux" paffinity component?
It turns out that there are *3* different implementations of the Linux
system call sched_setaffinity() (and 3 different corresponding
prototypes -- #@$@#$%!!!). The differences seem to be loosely
categorized as:
1. impleme
On Aug 15, 2005, at 8:37 AM, Gleb Natapov wrote:
This is actually an erroneous MPI program. MPI specifically states
that a buffer can be used for exactly one communication at a time.
This is actually the way MPI_Bcast works right now IMHO :)
Shhh!!
*Users* aren't allowed to do this. But w
On Mon, Aug 15, 2005 at 08:09:16AM -0400, Jeff Squyres wrote:
> On Aug 14, 2005, at 8:53 AM, Gleb Natapov wrote:
>
> > Lets say application wants to send buffer B to 100 other ranks. It does
> > 100 MPI_Isend (B).
>
> This is actually an erroneous MPI program. MPI specifically states
> that a b
On Aug 14, 2005, at 8:53 AM, Gleb Natapov wrote:
Lets say application wants to send buffer B to 100 other ranks. It does
100 MPI_Isend (B).
This is actually an erroneous MPI program. MPI specifically states
that a buffer can be used for exactly one communication at a time.
I don't know if
