Remove PERUSE in favour of upcoming MPI_T pvar implementation

[ompiteam]

Hello,

I suggest to remove the PERUSE functionality from the Open MPI trunk in favour of the upcoming MPI_T pvar implementation with the attached patch.
The PERUSE functionality is already broken as reported in https://svn.open-mpi.org/trac/ompi/ticket/4204.

Best regards
Christoph Niethammer

[ompiteam]

Imported from trac issue 4285. Created by hpcchris on 2014-02-18T05:09:25, last modified: 2014-02-18T06:45:10

• hpcchris attached Removed-peruse-functionality.patch on 2014-02-18 05:09:40

[ompiteam]

Trac comment by bosilca on 2014-02-18 06:34:42:

The PERSUE interface is providing a level of finesse and accuracy for retrieving the network status that is unmatched by the MPI_T, a functionality I need in some of our projects. I have no idea what the ticket https://svn.open-mpi.org/trac/ompi/ticket/4204 is about, but the PERUSE interface is working right now and it was working for quite some time.

For what is worth, I think this is way too early. Commits without careful validation break a functionality and instead of asking people to fix it, we remove it in favor of some upcoming functionality. Hardly a way to incite people to get involved.

[ompiteam]

Trac comment by bosilca on 2014-02-18 06:45:10:

The issue was with the test itself. a patch has been pushed into the testing.

[jsquyres]

PERUSE won't be removed until MPI_T can exhibit the same functionality. @hjelmn is working on a proposal for the MPI Forum Tools Working Group to add PERUSE-like capabilities to MPI_T.

[jsquyres]

This issue can be closed when #8057 merges.