<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Libbpf on Head First eBPF</title>
    <link>https://www.ebpf.top/tags/libbpf/</link>
    <description>Recent content in Libbpf on Head First eBPF</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>cn</language>
    <lastBuildDate>Mon, 19 Oct 2026 19:24:00 +0800</lastBuildDate>
    <atom:link href="https://www.ebpf.top/tags/libbpf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>跨发行版 eBPF 程序：兼容性负担与工程对策</title>
      <link>https://www.ebpf.top/post/maintaining-ebpf-prog/</link>
      <pubDate>Sun, 16 Aug 2026 19:51:40 +0800</pubDate>
      <guid>https://www.ebpf.top/post/maintaining-ebpf-prog/</guid>
      <description>本文地址：https://www.ebpf.top/post/maintaining-ebpf-prog 1. 背景：为何不能按用户态软件估算维护成本 2. 以 tracexec 工具维护为起点 3. 兼容性负担：按机制展开 3.1 Helper / kfunc 与 MSKV 3.2 可睡眠 fentry 与 CONFIG_FUNCTION_ERROR_INJECTION 3.3 架构差异：原子操作与 BPF JIT 3.4 带直接调用的动态 Ftrace 3.5 可睡眠程序与 BPF_F_NO_PREALLOC Map 3.6</description>
    </item>
  </channel>
</rss>
