<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kernel Nomad</title><link>https://kernelnomad.space/</link><description>Recent content on Kernel Nomad</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 12 Oct 2026 12:20:00 +0300</lastBuildDate><atom:link href="https://kernelnomad.space/index.xml" rel="self" type="application/rss+xml"/><item><title>A cache hit is only part of the story</title><link>https://kernelnomad.space/yazilar/cache-and-waiting/</link><pubDate>Mon, 12 Oct 2026 12:20:00 +0300</pubDate><guid>https://kernelnomad.space/yazilar/cache-and-waiting/</guid><description>&lt;h2 id="start-with-a-visible-request-path"&gt;Start with a visible request path&lt;/h2&gt;&#10;&lt;p&gt;The service lab has a short path to follow: a Python API, PostgreSQL for records, and Redis for a 60-second read cache.&lt;/p&gt;&#10;&lt;p&gt;Creating an item writes it to PostgreSQL. The first read retrieves it from the database and stores a cached copy. A second read can return the cached record. The response includes a &lt;code&gt;source&lt;/code&gt; field so the route is easy to see while experimenting.&lt;/p&gt;</description></item><item><title>Write the question before the benchmark</title><link>https://kernelnomad.space/yazilar/question-before-benchmark/</link><pubDate>Mon, 12 Oct 2026 12:10:00 +0300</pubDate><guid>https://kernelnomad.space/yazilar/question-before-benchmark/</guid><description>&lt;h2 id="what-would-the-number-mean"&gt;What would the number mean?&lt;/h2&gt;&#10;&lt;p&gt;Before timing a kernel, I want to write down the question that the timing is supposed to answer.&lt;/p&gt;&#10;&lt;p&gt;“Is this fast?” leaves a lot open. A narrower question is more useful: how does one change in the implementation affect the same workload, on the same device, with the same definition of elapsed time?&lt;/p&gt;</description></item><item><title>A small lab, a longer attention span</title><link>https://kernelnomad.space/yazilar/small-lab/</link><pubDate>Mon, 12 Oct 2026 12:00:00 +0300</pubDate><guid>https://kernelnomad.space/yazilar/small-lab/</guid><description>&lt;h2 id="a-useful-division-of-work"&gt;A useful division of work&lt;/h2&gt;&#10;&lt;p&gt;The Mac is the editing surface. The Ubuntu laptop is where the code runs.&lt;/p&gt;&#10;&lt;p&gt;That separation makes the environment concrete. Files live on the Linux machine, builds happen there, and a CUDA program runs against the GPU that is physically in that laptop.&lt;/p&gt;</description></item><item><title>A small lab, by design</title><link>https://kernelnomad.space/lab/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kernelnomad.space/lab/</guid><description>&lt;p&gt;The setup is simple: a Mac for editing, an Ubuntu laptop for execution, and an SSH connection between them. The Linux machine is also the home of this notebook.&lt;/p&gt;&#10;&lt;h2 id="the-machine"&gt;The machine&lt;/h2&gt;&#10;&lt;table&gt;&#10;&#9;&lt;thead&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Part&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Working setup&lt;/th&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/thead&gt;&#10;&#9;&lt;tbody&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Operating system&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Ubuntu 24.04 LTS&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;GPU&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;NVIDIA GTX 1050 Ti, 4 GB VRAM&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Memory&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;16 GB RAM&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Access&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;SSH and Tailscale&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Development&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;C++ / CUDA experiments on Linux&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;p&gt;The hardware gives me a concrete place to explore memory limits, resource sharing, and the difference between an idea and its execution.&lt;/p&gt;</description></item><item><title>Omer Isildak</title><link>https://kernelnomad.space/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kernelnomad.space/about/</guid><description>&lt;p&gt;I’m Omer Isildak. My focus is &lt;strong&gt;C++, CUDA, and inference systems&lt;/strong&gt;—understanding how software uses hardware and how models run as services.&lt;/p&gt;&#10;&lt;p&gt;Kernel Nomad is where I keep the technical notes, small experiments, and questions that come out of that work.&lt;/p&gt;</description></item></channel></rss>