<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Schedblame on Head First eBPF</title>
    <link>https://www.ebpf.top/tags/schedblame/</link>
    <description>Recent content in Schedblame on Head First eBPF</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>zh-CN</language>
    <lastBuildDate>Sun, 08 Nov 2026 10:49:09 +0000</lastBuildDate>
    <atom:link href="https://www.ebpf.top/tags/schedblame/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SchedBlame：容器等 CPU，到底是被谁抢占了？抢占了多久？</title>
      <link>https://www.ebpf.top/post/schedblame-culprit-cpu-contention-ebpf/</link>
      <pubDate>Sun, 08 Nov 2026 15:34:17 +0800</pubDate>
      <guid>https://www.ebpf.top/post/schedblame-culprit-cpu-contention-ebpf/</guid>
      <description>本文地址：https://www.ebpf.top/post/schedblame-culprit-cpu-contention-ebpf 1. 同样是容器变慢：先分清等调度、受限额和运行中受干扰 2. 先知道有没有在等：PSI 和运行队列延迟仍是排查入口 3. 已有方案各有所长：Netflix 看调</description>
    </item>
  </channel>
</rss>
