-
Notifications
You must be signed in to change notification settings - Fork 58
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
Documentation for writing a Kokkos connector? #92
Comments
@tpatki |
@zfrye-llnl : sorry that I missed you in the last message. You might also want to check out kokkos/kokkos#2422 , in which we're adding an autotuning extension to this interface. If it's feasible it might be interesting to develop a tool to minimize power without hurting performance, or things of that general flavor of optimization. That stuff is utterly undocumented for the moment, so we'd need to collaborate, but I'd be happy to look at it with the two of you. |
I would like to promote this github issue up as a priority for documentation of Kokkos Tools (using the new restructuredText format). Documentation of a Kokkos connector will be helpful for the ever-increasing vendor and open-source HPC tools available. In particular, this will be useful for autotuning tools available within the DoE along with new profiling and debugging tools available (in the last year) on leadership class supercomputers within the DoE. |
Now part of the Kokkos Tools tutorial. |
See the NERSC 2024 tutorial presentation on Kokkos to see the documentation / slides. I think the slides adequately provide information. If there is any other information anyone would like on documentation writing a Kokkos Tools connector, please feel free to request to reopen. Note this is an advanced topic and wouldn't be part of basic Kokkos Tools user documentation, which is a priority. |
@DavidPoliakoff
@zfrye-llnl and I are thinking of writing a Variorum connector for Kokkos (https://github.com/LLNL/variorum). Is there any documentation on how to write one (or which functions: initialize/finalize, push/pop, begin/end_parallel_for are mandatory)?
The text was updated successfully, but these errors were encountered: