From 66f933a9087451f05b4f60e88938e68f4eb20397 Mon Sep 17 00:00:00 2001
From: maleadt <maleadt@users.noreply.github.com>
Date: Mon, 27 May 2024 17:19:16 +0000
Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20=20@=2075254?=
 =?UTF-8?q?20538191cb9b7013a4f9d1dd55a4eabc0e7=20=F0=9F=9A=80?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 previews/PR44/post/2024-05-27-cuda_5.4/index.html | 2 +-
 previews/PR44/post/index.xml                      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/previews/PR44/post/2024-05-27-cuda_5.4/index.html b/previews/PR44/post/2024-05-27-cuda_5.4/index.html
index 7afcae4..e77643e 100644
--- a/previews/PR44/post/2024-05-27-cuda_5.4/index.html
+++ b/previews/PR44/post/2024-05-27-cuda_5.4/index.html
@@ -295,7 +295,7 @@ <h2 id="unified_memory_iteration"><a href="#unified_memory_iteration" class="hea
 julia&gt; # After
        @b foldl&#40;&#43;, a&#41;
 3.107 ms &#40;9 allocs: 208 bytes&#41;</code></pre>
-<p>These changes should make it easier to port applications to the GPU by incrementally moving parts of the codebase to the GPU without having to worry about the performance of accessing memory from the CPU. The only requirement is to use unified memory, e.g., by calling <code>cu</code> with <code>unified&#61;true</code>, or setting a global CUDA.jl preference to use unified memory by default. However, as unified memory comes with a slight cost, and results in synchronous allocation behavior, it is still recommended to switch back to regular device memory when your application has been fully ported to the GPU.</p>
+<p>These changes should make it easier to port applications to the GPU by incrementally moving parts of the codebase to the GPU without having to worry about the performance of accessing memory from the CPU. The only requirement is to use unified memory, e.g., by calling <code>cu</code> with <code>unified&#61;true</code>, or setting the CUDA.jl preference <code>default_memory</code> to use unified memory by default. However, as unified memory comes with a slight cost, and results in synchronous allocation behavior, it is still recommended to switch back to regular device memory when your application has been fully ported to the GPU.</p>
 <h2 id="other_changes"><a href="#other_changes" class="header-anchor">Other changes</a></h2>
 <p>To keep this post from becoming even longer, a quick rundown of other changes:</p>
 <ul>
diff --git a/previews/PR44/post/index.xml b/previews/PR44/post/index.xml
index 961e4e7..10443e3 100644
--- a/previews/PR44/post/index.xml
+++ b/previews/PR44/post/index.xml
@@ -150,7 +150,7 @@ julia&gt; @btime &#36;a&#91;&#93;;
 4.210 s &#40;9 allocs: 208 bytes, without a warmup&#41;julia&gt; # After
        @b foldl&#40;&#43;, a&#41;
 3.107 ms &#40;9 allocs: 208 bytes&#41;</code></pre>
-<p>These changes should make it easier to port applications to the GPU by incrementally moving parts of the codebase to the GPU without having to worry about the performance of accessing memory from the CPU. The only requirement is to use unified memory, e.g., by calling <code>cu</code> with <code>unified&#61;true</code>, or setting a global CUDA.jl preference to use unified memory by default. However, as unified memory comes with a slight cost, and results in synchronous allocation behavior, it is still recommended to switch back to regular device memory when your application has been fully ported to the GPU.</p>
+<p>These changes should make it easier to port applications to the GPU by incrementally moving parts of the codebase to the GPU without having to worry about the performance of accessing memory from the CPU. The only requirement is to use unified memory, e.g., by calling <code>cu</code> with <code>unified&#61;true</code>, or setting the CUDA.jl preference <code>default_memory</code> to use unified memory by default. However, as unified memory comes with a slight cost, and results in synchronous allocation behavior, it is still recommended to switch back to regular device memory when your application has been fully ported to the GPU.</p>
 <h2 id="other_changes">Other changes</h2>
 <p>To keep this post from becoming even longer, a quick rundown of other changes:</p>
 <ul>