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.

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

Disallow enabling both OpenMP and Threads in the same executable #406

Closed
dsunder opened this issue Aug 29, 2016 · 3 comments
Closed

Disallow enabling both OpenMP and Threads in the same executable #406

dsunder opened this issue Aug 29, 2016 · 3 comments
Labels
Enhancement Improve existing capability; will potentially require voting Feature Request Create new capability; will potentially require voting
Milestone

Comments

@dsunder
Copy link
Contributor

dsunder commented Aug 29, 2016

Many problems exist when enabling OpenMP and Threads in the same executable, one of which is that using the DefaultHostSpace can lead to the Threads execution space launching OpenMP threads.

@dsunder dsunder added Enhancement Improve existing capability; will potentially require voting Feature Request Create new capability; will potentially require voting labels Aug 29, 2016
@crtrott
Copy link
Member

crtrott commented Aug 30, 2016

I don't get what you mean with the Threads execution space launching OpenMP threads?

@hcedwar
Copy link
Contributor

hcedwar commented Aug 30, 2016

When using HostSpace views initialization is with the HostSpace::execution_space, which will be OpenMP. Thus using Threads instead of OpenMP when both are available leads to problems.
It is not a good idea to have both available in a single executable since if both are used there will be thread pool resource conflicts.

@crtrott
Copy link
Member

crtrott commented Aug 30, 2016

Yeah I know that. But what I don't get is why the Threads execution space would launch OpenMP threads. The scenario you describe the OpenMP space launches OpenMP threads.

@hcedwar hcedwar added this to the Backlog milestone Sep 30, 2016
@ibaned ibaned modified the milestones: Backlog, 2017-June-end Jun 14, 2017
@crtrott crtrott closed this as completed Jul 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Improve existing capability; will potentially require voting Feature Request Create new capability; will potentially require voting
Projects
None yet
Development

No branches or pull requests

4 participants