<?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>Golang on Sebastian PE — Go, AI &amp; Engineering</title>
    <link>https://triumphpc.github.io/blog/tags/golang/</link>
    <description>Recent content in Golang on Sebastian PE — Go, AI &amp; Engineering</description>
    <image>
      <title>Sebastian PE — Go, AI &amp; Engineering</title>
      <url>https://triumphpc.github.io/blog/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://triumphpc.github.io/blog/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 18 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://triumphpc.github.io/blog/tags/golang/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go Internals: sync.Mutex and sync/atomic — From Data Race to Starvation Mode</title>
      <link>https://triumphpc.github.io/blog/posts/sync-mutex-atomic/</link>
      <pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://triumphpc.github.io/blog/posts/sync-mutex-atomic/</guid>
      <description>Mutex and atomic are not two independent tools — they are one stack of abstractions. I dig through the stack from data race to starvation mode: why x++ is three ARM64 instructions, how CAS became a universal primitive (Herlihy 1991), why Mutex is built on top of atomic CAS, and how Russ Cox&amp;rsquo;s barging-vs-handoff debate (issue #13086) gave Go its 1ms starvation threshold. With public benchmarks, the bit layout of Mutex state, and a cheatsheet for when to reach for which.</description>
    </item>
  </channel>
</rss>
