Hello all .. apologies, but I missed today's ofiwg call. I understand that FABRIC_DIRECT w.r.t. libfabric 2.0 was discussed and it was determined that FABRIC_DIRECT would not be removed in the future. @Xiong, Jianxin<mailto:jianxin.xi...@intel.com> - could you summarize the rationale for this decision for me?
In the current "version2" PR (https://github.com/ofiwg/libfabric/pull/9384) the only providers that support FABRIC_DIRECT are opx, psm2, psm3 and tcp - however opx will drop support, and the psm2 provider could be removed entirely (TBD). The tcp provider is not optimized for latency (it is curious that it supports FABRIC_DIRECT at all). That leaves psm3 as the only provider that supports this feature. Does psm3 really need it? If not, then removing it would greatly simplify testing and maintenance costs - not just for ofiwg and the psm3 provider, but also for all middleware, etc. Thanks! Mike External recipient
_______________________________________________ ofiwg mailing list ofiwg@lists.openfabrics.org https://lists.openfabrics.org/mailman/listinfo/ofiwg
