<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Overlap on Sanketh's Blog</title><link>https://sankethbk.github.io/blog/tags/overlap/</link><description>Recent content in Overlap on Sanketh's Blog</description><generator>Hugo -- 0.166.0</generator><language>en-us</language><lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sankethbk.github.io/blog/tags/overlap/index.xml" rel="self" type="application/rss+xml"/><item><title>CUDA Streams and Host/Device Overlap</title><link>https://sankethbk.github.io/blog/posts/gpu/2026-09-02-2-cuda-streams/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate><guid>https://sankethbk.github.io/blog/posts/gpu/2026-09-02-2-cuda-streams/</guid><description>&lt;h1 id="cuda-streams-and-hostdevice-overlap"&gt;CUDA Streams and Host/Device Overlap&lt;/h1&gt;
&lt;p&gt;The &lt;a href="https://sankethbk.github.io/blog/gpu/2026-09-02-1-cuda-reduction"&gt;previous note&lt;/a&gt; covered reduction, the first parallel algorithm on the GPU side. This note moves to the &lt;strong&gt;host-device boundary&lt;/strong&gt;: how to keep the GPU busy while the CPU prepares the next batch of data, and how to overlap data movement with computation.&lt;/p&gt;
&lt;p&gt;So far, every kernel launch and every &lt;code&gt;cudaMemcpy&lt;/code&gt; has been synchronous. The host waits, the GPU works, the host waits again. CUDA &lt;strong&gt;streams&lt;/strong&gt; let you break that pattern.&lt;/p&gt;</description></item></channel></rss>