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

Request QUO_OBJ_NODE for next implemented QUO_get_comm_by_type #30

Open
dholladay00 opened this issue Nov 21, 2017 · 0 comments
Open

Request QUO_OBJ_NODE for next implemented QUO_get_comm_by_type #30

dholladay00 opened this issue Nov 21, 2017 · 0 comments

Comments

@dholladay00
Copy link

dholladay00 commented Nov 21, 2017

Giving applications that want to map between a 1 rank/core policy to a 1 rank/NUMA policy an on-numa-node communicator would be a good choice for the next implemented type in QUO_get_comm_by_type. This is a good choice in my mind because it alleviates the need for OpenMP applications to deal with first touch and keeps the cores/rank at a level in which on-node gathers/scatters are manageable.

Not necessarily a high priority issue, but if I had a say in which one gets implemented next, that would be my vote.

Edit: grammar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant