One question that I had in the back of my had a while ago was whether
the functionality of the topo framework needs to be adapted to support
the new MPI 2.2 graph topology functions? Maybe this can be taken into
consideration as well...
Thanks
Edgar
Jeff Squyres wrote:
WHAT: Revamp the topo base to make it like the rest of the OMPI frameworks.
WHY: topo was written way back at the beginning of time and is showing
its age (i.e., other frameworks have advanced while topo has not).
Someone is interested in possibly writing a new topo component, so it
seems an opprotune time to revamp the framework (i.e., before they start).
WHERE: Mostly in ompi/mca/topo, but some in ompi/communicator/, too
WHEN: 1.5.x sometime
TIMEOUT: Next Tuesday teleconf; Nov 3
More details
------------
Per http://www.open-mpi.org/community/lists/devel/2009/10/7041.php,
there are some shortcomings to the topo framework. It pretty much
reflects the fact that it was written way back near the beginning of the
ompi project and has not been updated since.
I'd like to revamp it to have OBJ-based modules, per-communicator
component/module selections, etc. This would be similar to (but simpler
than) the coll framework.
I've started an hg for this work:
http://bitbucket.org/jsquyres/ompi-topo-fixes/
Comments?
--
Edgar Gabriel
Assistant Professor
Parallel Software Technologies Lab http://pstl.cs.uh.edu
Department of Computer Science University of Houston
Philip G. Hoffman Hall, Room 524 Houston, TX-77204, USA
Tel: +1 (713) 743-3857 Fax: +1 (713) 743-3335
