I do not know if there is any documentation on btl/vader.

The use of btl/vader by collective communications can be summarize as:
Collective communication algorithms in coll/base, called by coll/tuned, use 
pt2pt communications as base operations.
Point-to-point operations are handled by the pml framework.
Coll/tuned does not interact directly with btl/vader: it uses pt2pt 
communications handled by pml/ob1 which can rely on btl/vader for intra-node 


P.S.: Note that btl/vader is renamed btl/sm in v5.x versions.

De : devel <devel-boun...@lists.open-mpi.org> De la part de zhiting zhu via 
Envoyé : vendredi 21 avril 2023 21:02
À : devel@lists.open-mpi.org
Cc : zhiting zhu <zhiti...@cs.utexas.edu>
Objet : [OMPI devel] algorithm description of shared memory(vader) btl


Is there any algorithm/high level description on how the shared memory(vader) 
btl components work? I'm wondering about the part that does CICO using shared 
memory, not the part that uses single copy with kernel support. How does the 
collective communication algorithm use the vader btl? Thanks!


Reply via email to