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?
--
Jeff Squyres
jsquy...@cisco.com
