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

CP013: Affinity between execution and memory resource #42

Open
hcedwar opened this issue Apr 16, 2018 · 2 comments
Open

CP013: Affinity between execution and memory resource #42

hcedwar opened this issue Apr 16, 2018 · 2 comments
Assignees
@hcedwar
Labels
SAN18 San Diego 2018 C++ Meeting

Comments

@hcedwar
Copy link
Collaborator

hcedwar commented Apr 16, 2018

Affinity has affinity_query between two execution resources. Recommend this be between an execution resource and a memory resource.
@hcedwar hcedwar changed the title Affinity between execution and memory resource CP013: Affinity between execution and memory resource Apr 26, 2018
@hcedwar hcedwar added the RAP18 Rapperswil 2018 C++ Meeting label Apr 26, 2018
@hcedwar
Copy link
Collaborator Author

hcedwar commented May 3, 2018

Querying an affinity metric should be between an execution resource and a memory resource.
Querying an affinity metric between two execution resources would be transitive: "what is our affinity with the most-local memory resource we have in common."

hcedwar added a commit to hcedwar/standards-proposals that referenced this issue May 4, 2018
@hcedwar
Address CP013 issues codeplaysoftware#41, codeplaysoftware#42, codepl…
b0e12c0 
…aysoftware#50.
hcedwar added a commit to hcedwar/standards-proposals that referenced this issue May 6, 2018
@hcedwar
Address CP013 issues codeplaysoftware#41, codeplaysoftware#42, codepl…
0a15f5d 
…aysoftware#50.
@pblinzer
Copy link

The affinity metric should have also some qualifier attribute mechanisms, e.g. for some heterogeneous execution resources, the availability of global atomicsOps or cc property on "nearest common memory resource" may not be there.

@AerialMantis AerialMantis added SAN18 San Diego 2018 C++ Meeting and removed RAP18 Rapperswil 2018 C++ Meeting labels Jul 23, 2018
AerialMantis pushed a commit to AerialMantis/standards-proposals that referenced this issue Oct 7, 2018
Issue codeplaysoftware#41: Separate execution and memory resources.
2abd3fb 
* Fixes codeplaysoftware#41 and codeplaysoftware#42.
* Introduce `memory_resource` to represent the memory component of a system topology.
* Remove `can_place_memory` and `can_place_agents` from the `execution_resource` as these are no longer required.
* Remove `memory_resource` and `allocator` from the `execution_context` as these no longer make sense.
* Update the wording to describe how execution resources and memory resources are structured.
* Refactor `affinity_query` to be between an `execution_resource` and a `memory_resource`.
* Make minor corrections.
@AerialMantis AerialMantis mentioned this issue Oct 7, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hcedwar hcedwar

Labels
SAN18 San Diego 2018 C++ Meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pblinzer @hcedwar @AerialMantis