From 3c83dddda18f559a91b75f94c47b3ea1a55b05c3 Mon Sep 17 00:00:00 2001 From: Greg Lueck Date: Thu, 18 Jul 2024 13:56:24 -0400 Subject: [PATCH] Merge pull request #583 from bader/mem_advise Fix the link to the table with mem_advice and prefetch method descriptions. --- adoc/chapters/programming_interface.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/adoc/chapters/programming_interface.adoc b/adoc/chapters/programming_interface.adoc index c7e06bd0..f97f72f7 100644 --- a/adoc/chapters/programming_interface.adoc +++ b/adoc/chapters/programming_interface.adoc @@ -10179,7 +10179,7 @@ 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 <> and +More about [code]#prefetch# is found in <> and <>. If a device supports concurrent access to shared allocations, then [code]#prefetch# operations may be overlapped with kernel execution. @@ -10187,7 +10187,7 @@ If a device supports concurrent access to shared allocations, then 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 <> and <> for more +See <> and <> for more information. In the most capable systems, users do not need to use SYCL USM allocation