Nathan,
Thank you for your reply. I opened an issue:
https://github.com/open-mpi/ompi/issues/4434
Thanks,
Joseph
On 11/02/2017 01:04 PM, Nathan Hjelm wrote:
Hmm, though I thought we also make calls to opal_progress () in your case
(calling MPI_Win_lock on self). Open a bug on github and I w
Hmm, though I thought we also make calls to opal_progress () in your case
(calling MPI_Win_lock on self). Open a bug on github and I will double-check.
> On Nov 1, 2017, at 9:54 PM, Nathan Hjelm wrote:
>
> This is a known issue when using osc/pt2pt. The only way to get progress is
> to enable
This is a known issue when using osc/pt2pt. The only way to get progress is to
enable (it is not on by default) it at the network level (btl). How this is
done depends on the underlying transport.
-Nathan
> On Nov 1, 2017, at 9:49 PM, Joseph Schuchart wrote:
>
> All,
>
> I came across what I
All,
I came across what I consider another issue regarding progress in Open
MPI: consider one process (P1) polling locally on a regular window (W1)
for a local value to change (using MPI_Win_lock+MPI_Get+MPI_Win_unlock)
while a second process (P2) tries to read from a memory location in a
dyn
