Sorry, I missed the 4.0 on the PR (despite being the first thing in the title).
George.
> On Sep 20, 2018, at 22:15 , Ralph H Castain wrote:
>
> That’s why we are leaving it in master - only removing it from release branch
>
> Sent from my iPhone
>
> On Sep 20, 2018, at 7:02 PM, George
That’s why we are leaving it in master - only removing it from release branch
Sent from my iPhone
> On Sep 20, 2018, at 7:02 PM, George Bosilca wrote:
>
> Why not simply ompi_ignore it ? Removing a component to bring it back later
> would force us to lose all history. I would a rather add an
Why not simply ompi_ignore it ? Removing a component to bring it back later
would force us to lose all history. I would a rather add an .ompi_ignore
and give an opportunity to power users do continue playing with it.
George.
On Thu, Sep 20, 2018 at 8:04 PM Ralph H Castain wrote:
> I already
I already suggested the configure option, but it doesn’t solve the problem. I
wouldn’t be terribly surprised to find that Cray also has an undetected problem
given the nature of the issue - just a question of the amount of testing,
variety of environments, etc.
Nobody has to wait for the next
I understand and agree with your point. My initial email is just out of
curiosity.
Howard tested this BTL for Cray in the summer as well. So this seems to
only affected OPA hardware.
I just remember that in the summer, I have to make some change in libpsm2
to get this BTL to work for OPA. Maybe
I suspect it is a question of what you tested and in which scenarios. Problem
is that it can bite someone and there isn’t a clean/obvious solution that
doesn’t require the user to do something - e.g., like having to know that they
need to disable a BTL. Matias has proposed an mca-based
In the summer, I tested this BTL with along with the MTL and able to use
both of them interchangeably with no problem. I dont know what changed.
libpsm2?
Arm
On Thu, Sep 20, 2018, 7:06 PM Ralph H Castain wrote:
> We have too many discussion threads overlapping on the same email chain -
> so
We have too many discussion threads overlapping on the same email chain - so
let’s break the discussion on the OFI problem into its own chain.
We have been investigating this locally and found there are a number of
conflicts between the MTLs and the OFI/BTL stepping on each other. The correct
