[ofa-general] [PATCH 2/3] OpenSM: Fix incorrect reporting of routing engine used

Al Chu chu11 at llnl.gov
Tue Dec 18 16:41:34 PST 2007


Hey Sasha,

This patch 2/3 fixes the incorrect reporting of what routing engine was
used in the logs and in the console.  Based on which routing engine
succeeded in osm_ucast_mgr_process(), the result is stored in the
'routing_engine_used' and that result is used for the eventual output.
The lock in print_status() is across all p_osm data now and now uses
p_osm->lock.  The logic has been reverted in osm_ucast_mgr_process().

Some "special case" handling had to be done in osm_ucast_mgr_process()
to determine if a routing engine suceeded or failed.  It's not pretty.
I figure when routing engine chains are supported later on some re-org
in the routing engine code will have to be done, so this could be fixed
more properly at that time.

Thanks,
Al

-- 
Albert Chu
chu11 at llnl.gov
925-422-5311
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-fix-incorrect-reporting-of-routing-engine.patch
Type: text/x-patch
Size: 4466 bytes
Desc: not available
URL: <http://lists.openfabrics.org/pipermail/general/attachments/20071218/c450897b/attachment.bin>


More information about the general mailing list