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
Default pool rename #2926
Default pool rename #2926
Conversation
@@ -361,7 +361,7 @@ namespace hpx { namespace resource { namespace detail | |||
// exclusively if dynamic pools are enabled. | |||
// Also, by default, the first PU is always exclusive | |||
// (to avoid deadlocks). | |||
add_resource(p, "default", | |||
add_resource(p, initial_thread_pools_[0].pool_name_, |
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.
May I suggest you use the get_default_pool_name()
member function everywhere here instead of the initial_thread_pools_[0].pool_name_
you currently use?
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.
inside detail::partitioner I used initial_thread_pools_[0].pool_name, but outside it, I used get_default_pool_name. Not a big deal. I will change it.
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.
LGTM, thanks!
Users might want to create numa-pool-0, numa-pool-1 etc and rename the default pool to one of them to make it easier to loop over pools in code and not treat pool 0 specially.
91fbdb9
to
aed39b3
Compare
this fixes #2925