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

Which device properties should we expose to the user? #23638

Open
e-kayrakli opened this issue Oct 12, 2023 · 2 comments · May be fixed by #25945
Open

Which device properties should we expose to the user? #23638

e-kayrakli opened this issue Oct 12, 2023 · 2 comments · May be fixed by #25945
Labels
area: GPU Support type: Design type: Feature Request

Comments

@e-kayrakli
Copy link
Contributor

GPUs have several characteristics that can be queried by the application. But there a lot of them, and most of them should be irrelevant to the user. Which ones are important and should be exposed to the user?

The following can help with the application logic:

Maybe the following can help with diagnostics:

  • memoryBusWidth/memoryClockRate
@e-kayrakli
Copy link
Contributor Author

I imagine we can expose them as methods/fields in the locale type. Currently, we can't do here in GPU kernels, so it may require us to do an interim solution first. (#22147)

@psath psath mentioned this issue Oct 19, 2023
Open
@razoumov
Copy link

I would add a variable identifying the device, e.g. something like "Tesla P100-PCIE-12GB" returned by nvidia-smi -- this would be very useful on a heterogeneous HPC cluster with multiple GPU types. Not sure if char cudaDeviceProp::name returns that information, but something along those lines.

@stonea stonea linked a pull request Sep 13, 2024 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area: GPU Support type: Design type: Feature Request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add various GPU device query functions stonea/chapel
2 participants
@e-kayrakli @razoumov