>> That doesn't really explain anything. How is opensm using this >> value, and what assumptions does it make about its size? We should >> make sure that we have the right fix here. > >Why are you being so difficult to work with here?
You're asking to change code with zero explanation as to why the code needs to change. >OpenSM 3.2.? added the value to umad.h file and referenced it in >osm_vendor_umad.c. >If you have issues with the code, then take it up with those who wrote the code >and stop impeding forward progress of getting a sorely needed newer revision of >OpenSM to the Windows community. If you want to change the windows version of libibumad, then submit a patch against that code with a reason why that change is needed. The #define that you gave in the patch is wrong. The limit is much, much higher on windows. - Sean _______________________________________________ ofw mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
