On the call today, no one had any objections to bringing this stuff to
the trunk. v1.2.9 and v1.3.0 releases have a higher priority, so I'll
bring this stuff over to the trunk when those two releases are done
(hopefully tomorrow!).
On Jan 10, 2009, at 2:21 PM, Jeff Squyres wrote:
FWIW, I
FWIW, I've finished a first cut of this stuff. I'll provide an
overview on next Tuesday's teleconf.
I didn't "fix" MPI_REPLACE yet (it does seem to be a different issue;
I mainly extended what was already there) but I've done most of the
rest of the work:
- Created a new op framework tha
On Jan 5, 2009, at 10:09 AM, Brian W. Barrett wrote:
I think this sounds reasonable, if (and only if) MPI_Accumulate is
properly handled. The interface for calling the op functions was
broken in some fairly obvious way for accumulate when I was writing
the one-sided code. I think I had to
I think this sounds reasonable, if (and only if) MPI_Accumulate is
properly handled. The interface for calling the op functions was broken
in some fairly obvious way for accumulate when I was writing the one-sided
code. I think I had to call some supposedly internal bits of the
interface to m
WHAT: Converting the back-end of MPI_Op's to use components instead of
hard-coded C functions.
WHY: To support specialized hardware (such as GPUs).
WHERE: Changes most of the MPI_Op code, adds a new ompi/mca/op
framework.
WHEN: Work has started in an hg branch (http://www.open-mpi.org/hg/h
