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
Resource manager fixes #2623
Resource manager fixes #2623
Conversation
e64bfa5
to
ff1eff2
Compare
- adding missing code - adding test - thread_pool_executors now report real number of assigned cores
- flyby changes necessary to make HPXrx work # Conflicts: # hpx/runtime/threads/detail/scheduling_loop.hpp
# Conflicts: # hpx/runtime/threads/detail/scheduling_loop.hpp
ff1eff2
to
f3bf350
Compare
f3bf350
to
6c3348a
Compare
{ | ||
for (int i = 0; i != num_tasks; ++i) | ||
{ | ||
traits::apply_execute(exec, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could this use the new executor interface instead?
{ | ||
for (int i = 0; i != num_tasks; ++i) | ||
{ | ||
traits::apply_execute(exec, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could this use the new executor interface instead?
@sithhell Your comments have been addressed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, LGTM now.
A couple of fixes I had lying around for a while in my local copy of the repository.
This improves the behavior of the resource-manager in cases where the user requests more resources than available.