oneapi-src / oneapi-src/unified-runtime

Atomic Operations Device and System Memory Scope Support for HIP

Open
#2,296 0 comments 0 reactions 1 assignee View on GitHub

@npmiller is already working on this.

Since Nov 8, 2024.

hip
Dominant language
C++
Stars
57
Forks
120
Avg merge
1d 14h
Merged PRs (30d)
1

Description

In an hacky attempt tried to enable the device and system memory scope support for AMD MI210 GPU reverting the commit
https://github.com/oneapi-src/unified-runtime/commit/9947a817291628ad6d61e102e1d2bd783c041c19 to the https://github.com/oneapi-src/unified-runtime/commit/08b19b224c0be9cdd2073de080a3e654600007f1 but it didn't work out for 2 GPU system. The same code I run at level_zero 2GPU failed with AMD GPU at random iterations due to inconsistencies.

I was wondering is there an easy way to have consistent device and system wide atomic memory_scope ?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.