Hui Zhou
Hui Zhou
> We continued discussing this on Slack, but I want to slurp in that this should probably be an allreduce for a few reasons, most notably because there are some...
I think the `allgather` option probably is the most flexible one. However, I would hate to run one collective per hint key. So I am thinking we can run a...
What optimizations are you having in mind?
I see. What I was envisioning is to enable those runtime optimizations as runtime switch: ``` if (comm->hints[MPIR_COMM_HINT_NO_ANY_SOURCE]) { [optimization branch] } ``` The idea is the consistency check will...
That means the key `allow_overtaking` has a consistency requirement. So we will check the consistency at `MPII_Comm_set_hints` time so that hint will never be inconsistent (or error at setting time)....
> I don't know how `allreduce(sum)` will help. We should probably add an internal op called `is_equal`. That sounds like a good idea.
How much impact if we extend hydra/PMI1 to allow binary put/get? I would really like not to have to maintain two different mechanisms.
How about we treat it similar to MPIX, use the extended feature only if the Process manager supports it, otherwise we fallback. The fallback should allow the transition before the...
> > > So add a 4th and 5th put/get implementation? No. Just one put/get with hex encoding and maximum value length (the fall back version) and another put/get with...
> > > So add a 4th and 5th put/get implementation? > > > > > > No. Just one put/get with hex encoding and maximum value length (the fall...