Hello,
In branches\opensm_3\ you will find OpenSM 3.3.3 suitable to be dropped into
a build tree as trunk\ulp\opensm_3 and built for all architectures/OS-flavors.
One needs to be careful as the .exe files [opensm.exe, osmtest.exe &
ibtrapgen.exe] are currently the same names as produced by building in
trunk\ulp\opensm.
Given previous discussions on how to move forward with a new version of opensm
and yet retain the past version in case of emergency.
Where emergency is defined as at some installation the new version of opensm
does not render the fabric usable where the old version did; unlikely but
possible. Without an escape hatch a customer is without recourse.
I'd like to propose the following svn src file structure changes until the
WinOF 2.3 time frame.
trunk\ulp\opensm\user --> trunk\ulp\opensm\userO
branches\opensm_3\user --> trunk\ulp\opensm\user
Now we have
trunk\ulp\opensm\userO current opensm version @ 3.0.0 base.
trunk\ulp\opensm\user New opensm version # 3.3.3
Additionally the SOURCES files in the trunk\ulp\opensm\userO\* would be
modified to append the letter 'O' to the .exe filename to distinguish them from
new version; examples:
opensmO.exe
osmtestO.exe
ibtrapgenO.exe
This could be abbreviated to just building opensmo.exe.
With the new 3.3.3 version of openSM the diffs between the latest OFED (3.3.3)
and the Windows version are not so overwhelming and can be managed in place;
point being the trunk\ulp\opensm\userO is a life-saver until full confidence is
gained in the new opensm implementation.
Your thoughts?
Thank you,
Stan.
_______________________________________________
ofw mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
