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.

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

Fix the link to the table with mem_advice and prefetch method descriptions. #583

Merged
merged 1 commit into from
Jul 18, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions adoc/chapters/programming_interface.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -10179,15 +10179,15 @@ enqueueing [code]#prefetch# operations on a device.
These operations inform the SYCL runtime that the specified shared allocation is
likely to be accessed on the device in the future, and that it is free to
migrate the allocation to the device.
More about [code]#prefetch# is found in <<table.members.queue>> and
More about [code]#prefetch# is found in <<table.queue.shortcuts>> and
<<table.members.handler.copy>>.
If a device supports concurrent access to shared allocations, then
[code]#prefetch# operations may be overlapped with kernel execution.

Additionally, users may use the [code]#mem_advise# member function to annotate
shared allocations with [code]#advice#.
Valid [code]#advice# is defined by the device and its associated backend.
See <<table.members.queue>> and <<table.members.handler.copy>> for more
See <<table.queue.shortcuts>> and <<table.members.handler.copy>> for more
bader marked this conversation as resolved.
Show resolved Hide resolved
information.

In the most capable systems, users do not need to use SYCL USM allocation
Expand Down