Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: [OMPI devel] RFC: revamp topo framework
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2009-10-28 10:20:00


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
jsquyres_at_[hidden]