<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bpf on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/bpf/</link>
    <description>Recent content in Bpf on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/bpf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux BPF Schedulers — sched_ext, scx_rusty, and scx_bpfland Guide</title>
      <link>https://www.pistack.xyz/posts/2026-05-23-self-hosted-linux-bpf-schedulers-sched-ext-scx-rusty-lavd-bpfland-guide/</link>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-23-self-hosted-linux-bpf-schedulers-sched-ext-scx-rusty-lavd-bpfland-guide/</guid>
      <description>&lt;p&gt;Linux CPU scheduling has historically been a kernel-only concern — you picked a scheduler (CFS, MuQSS, BFS) at compile time or patched your kernel, and lived with it. The &lt;strong&gt;sched_ext&lt;/strong&gt; (scx) framework changes that paradigm entirely by exposing the Linux CPU scheduler as a programmable &lt;strong&gt;eBPF&lt;/strong&gt; interface. This means you can load, unload, and switch schedulers at runtime without recompiling the kernel.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
