all trees should be pe/node/physnode/network topology aware
There are various places in Charm++ where broadcast and reduction trees are implemented as PE n to PEs 2*n+1 and 2*n+2 (or the obvious k-way extension). These should in all instances be replaced with a standard tree that aggregates communication hierarchically within a PE, node, physical node, and finally whatever network topology can be detected. It doesn't need to be perfect at first, but we do need a single tree-generating utility that can be called everywhere that this kind of tree is needed.
#10 Updated by Juan Galvez about 2 years ago
- Status changed from In Progress to Implemented