Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make sure opal_start_thread always spawns pthreads #9326

Merged
merged 1 commit into from
Sep 14, 2021
Merged

Make sure opal_start_thread always spawns pthreads #9326

merged 1 commit into from
Sep 14, 2021

Commits on Aug 27, 2021

  1. Make sure opal_start_thread always spawns pthreads 

    Users of `opal_start_thread` (btl/tcp, ft, smcuda, progress thread)
may spawn threads that may block in functions unaware of argobots
or qthreads (e.g., libevent or read(3)). If we spawn an argobot or
qthread instead of a pthread the thread executing the argobot or
qthread (potentially the main thread) blocks, leading to a deadlock
situation. Open MPI expects the semantics of a pthread so
we should handle all internal threads as such.

Signed-off-by: Joseph Schuchart <[email protected]>
    @devreal
    devreal committed Aug 27, 2021
    Configuration menu
    Copy the full SHA
    e3ca132 View commit details
    Browse the repository at this point in the history