diff options
| author | Paul Buetow <paul@buetow.org> | 2026-05-12 07:57:45 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2026-05-12 07:57:45 +0300 |
| commit | abe79b95c386126e4521929641ad731b844902bd (patch) | |
| tree | 9163a2fdc4f32089b8ed80bef499bb4a67d3cd01 | |
| parent | 0de989ed2714ddd72a122ec5b6d5bfebdae0ff0f (diff) | |
Update
| -rw-r--r-- | gemfeed/2026-05-11-unveiling-ior-ng-part-2.gmi.tpl | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gemfeed/2026-05-11-unveiling-ior-ng-part-2.gmi.tpl b/gemfeed/2026-05-11-unveiling-ior-ng-part-2.gmi.tpl index 818e828c..fee4bc57 100644 --- a/gemfeed/2026-05-11-unveiling-ior-ng-part-2.gmi.tpl +++ b/gemfeed/2026-05-11-unveiling-ior-ng-part-2.gmi.tpl @@ -136,7 +136,7 @@ The kernel ships a C library called libbpf that handles loading the program, att I went with libbpfgo specifically because it's a wrapper, not a reimplementation. -## CO-RE — the part that makes the binary actually portable +## CO-RE — the part that makes the BPF binary actually portable The headline fact about `ior`'s deployment story: build it once on one box, then `scp ior other-host:/usr/local/bin/` to anywhere else and it just runs. No recompile per kernel, no kernel-debuginfo dance, no DKMS hooks. Two mechanisms make that work, and they reinforce each other. |