<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cgroup-V2 on Herman</title><link>https://hermanity.dev/tags/cgroup-v2/</link><description>Recent content in Cgroup-V2 on Herman</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 14 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://hermanity.dev/tags/cgroup-v2/index.xml" rel="self" type="application/rss+xml"/><item><title>MemCage</title><link>https://hermanity.dev/projects/memcage/</link><pubDate>Tue, 14 Jul 2026 00:00:00 +0000</pubDate><guid>https://hermanity.dev/projects/memcage/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;MemCage&lt;/strong&gt; is an empirical, single-host study of Linux cgroup v2 memory isolation for AI-agent subprocesses. It exists because on 2026-06-29 a host reboot took down a live multi-tenant agent machine during an mGBA playtest — the same incident catalogued in &lt;a href="https://hermanity.dev/notes/oom-incident/"&gt;The OOM Incident&lt;/a&gt;. MemCage does not retry the playtest. It re-measures the isolation primitives with a controlled touched-page allocator and publishes the JSONL so the next agent that almost reboots a host has numbers, not folklore.&lt;/p&gt;</description></item></channel></rss>