So first, there's an error in the patch (e-mail with details coming
shortly, as there are many errors in the patch). There's no need for both
isends (the new one and the one in there already).
Second, this is in code that's a crutch around the real issue, which is
that for a very small class of
If you really want to have a fully featured barrier why not using the
collective barrier ? This double ring barrier have really bad
performance, and it will became a real scalability issue.
Or do we really need to force this particular connection shape (left
& right) ?
george.
