Re: [ofiwg] libfabric 2.0 and FABRIC_DIRECT

Got it, thanks! From: Xiong, Jianxin Sent: Tuesday, February 20, 2024 5:00 PM To: Blocksome, Michael ; ofiwg@lists.openfabrics.org Subject: RE: libfabric 2.0 and FABRIC_DIRECT FABRIC_DIRECT is a building option that providers can choose to support or not. Providers are free to remove

[ofiwg] libfabric 2.0 and FABRIC_DIRECT

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 - could you summarize the rationale for this

Re: [ofiwg] inserting duplicate addresses into an AV

day, March 20, 2018 1:38 PM To: Blocksome, Michael <michael.blocks...@intel.com>; ofiwg@lists.openfabrics.org Subject: RE: inserting duplicate addresses into an AV The failures are related to MPI spawn tests. This happens with Intel MPI, but I suspect MPICH or other MPIs may have

Re: [ofiwg] Libfabric v1.4.1 release

Jeff, Is it possible to seed a new provider feature matrix for v1.5 development now that v1.4.1 has been released? Also, can't this feature matrix be compiled from the libfabric source instead of by hand-editing a wiki page? Seems like each provider only needs to have some "feature" data