bosilca

One of the root causes of this is that we `dlclose` a component where we successfully called `_init`, so we basically never give the component a chance to cleanup behind...

This change in API will break the MPI datatype management in many ways (basically everything that relies on the datatype storage description such as one-sided, IO, and all the datatype...

The only thing you control via these MCA parameters is the port for the listening fd, all other ports are decided by the kernel.

How would OMPI know what the packets look like ? Moreover, I don't think there is a way to force a specific port on the socket returned from accept/connect. Also,...

I shall better know I wrote a big chunk of that code :cold_sweat: What I don't understand is what more can we offer taking in account what we already offer...

Not all APIs will need to be doubled. All API handling a single `count` and `disps` (per buffer) can simply be extended to take the larger count into account. However,...

This is also a possible approach, but not the one I was going for. My idea would have doubled the size of the coll structure and a little code in...

The `pmix` MCA param would not make sense, and you already moved `pmix_base_async_modex`, `pmix_base_collect_data` and `pmix_base_exchange_timeout`. While leaves a single, somewhat important MCA param out, the `pmix_base_verbose`. But as we...

We skipped all the connect/accept/spawn tests for years, that's why we are in this mess.

This storyline (nobody uses this feature) is getting old. I had similar contact as @dalcinl, people tried to use but it was broken so they found another way. I have...