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

Fix typo #330

Merged
merged 1 commit into from Mar 3, 2023
Merged

Fix typo #330

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/source/usecases/Moving_from_EnableUVM_to_SharedSpace.md
View file
Open in desktop
Expand Up @@ -5,7 +5,7 @@ The accesses in `parallel_for`, `parallel_reduce`, or `parallel_scan` do not occ

## The alternative

We introduced a new alias named [`SharedSpace`](SharedSpace) in Kokkos 4.0. This always points to memory that is accessible by every [`ExecutionSpace`](ExecutionSpaceConcept) and is migrated without user interaction to the acessing `ExecutioSpace` on demand. After migration the memory is accessed locally.
We introduced a new alias named [`SharedSpace`](SharedSpace) in Kokkos 4.0. This always points to memory that is accessible by every [`ExecutionSpace`](ExecutionSpaceConcept) and is migrated without user interaction to the acessing `ExecutionSpace` on demand. After migration the memory is accessed locally.
Using the alias e.g. in `Views` is expressive and thus easier to read. Furthermore, it is portable to every backend that can automatically migrate memory between `ExecutionSpaces`.
Furthermore, we introduced the alias [`SharedHostPinnedSpace`](SharedHostPinnedSpace) which points to memory that is accessible by all enabled `ExecutionSpaces` but always resides in the memory of the host.

Expand Down