<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kernel on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/kernel/</link><description>Recent content in Kernel on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 06 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/kernel/index.xml" rel="self" type="application/rss+xml"/><item><title>How Linux Cgroups v1 vs v2 Works: Deep Dive into Internals</title><link>https://ai-blog.noorshomelab.dev/how-it-works/how-linux-cgroups-v1-v2-works/</link><pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/how-it-works/how-linux-cgroups-v1-v2-works/</guid><description>&lt;p&gt;The smooth operation of modern cloud infrastructure, from simple Docker containers to complex Kubernetes clusters, hinges on a fundamental Linux kernel feature: Control Groups, or cgroups. Without cgroups, a single runaway process could starve an entire system of CPU, memory, or I/O, leading to instability and service outages. Understanding the evolution from cgroups v1 to cgroups v2 is crucial for anyone managing containerized workloads, as it represents a significant architectural shift with profound implications for resource predictability, isolation, and overall system performance.&lt;/p&gt;</description></item></channel></rss>