FYI: at the meeting in Paris this week, we decided that it would be a
good idea to consolidate some "utility" IB code into mca/common/of
(OpenFabrics) so that it could be shared among multiple components
(e.g., some IB-specific collective components).
Exactly what will be moved into common
Jeff Squyres wrote:
FYI: at the meeting in Paris this week, we decided that it would be a
good idea to consolidate some "utility" IB code into mca/common/of
(OpenFabrics) so that it could be shared among multiple components
(e.g., some IB-specific collective components).
Exactly what wil
On Oct 6, 2007, at 9:08 PM, Andrew Friedley wrote:
Yeah so the HCA querying/selecting will be good to have separate, as
well as PD/registration stuff -- for example I copied the mpool rdma
callback functions verbatim from the OpenIB BTL to the UD BTL. I
don't
think QP creation is worth shari
Jeff Squyres wrote:
On Oct 6, 2007, at 9:08 PM, Andrew Friedley wrote:
Yeah so the HCA querying/selecting will be good to have separate, as
well as PD/registration stuff -- for example I copied the mpool rdma
callback functions verbatim from the OpenIB BTL to the UD BTL. I
don't
think QP
On Oct 6, 2007, at 9:59 PM, Andrew Friedley wrote:
Yes, I very much care about backward compatibility of the openib name
and MCA parameters... This is, as I see it, the biggest issue with
changing the name. Stuff like this has to work:
mpirun --mca btl openib,self ...
mpirun -
Jeff Squyres wrote:
On Oct 6, 2007, at 9:59 PM, Andrew Friedley wrote:
Yes, I very much care about backward compatibility of the openib name
and MCA parameters... This is, as I see it, the biggest issue with
changing the name. Stuff like this has to work:
mpirun --mca btl openib,s
