#Cgroup
Durch strukturelle Vorgaben lässt sich bei cgroup v2 festlegen, welche Controller für ein bestimmtes cgroup aktiv sind.
https://docs.kernel.org/admin-guide/cgroup-v2.html
November 17, 2026 at 8:08 AM
Anna Arpaci-Dusseau: Benchmarking Linux CGroup and Schedule Idle https://arxiv.org/abs/2611.23655 https://arxiv.org/pdf/2611.23655 https://arxiv.org/html/2611.23655
November 19, 2026 at 6:43 AM
Er ordnet z. B. CPU‑Zeit oder Speicherplatz den jeweiligen cgroup‑Untergruppen zu.
https://docs.kernel.org/admin-guide/cgroup-v2.html
November 13, 2026 at 8:00 AM
#hwloc 2.16.0 released with improvements for new Apple CPUs, Intel CPUs, Windows support, several Cgroup fixes for Linux, and many more. #HPC #locality
Available from www.open-mpi.org/projects/hwl...
sympa.inria.fr/sympa/arc/hw...
Portable Hardware Locality (hwloc)
www.open-mpi.org
November 19, 2026 at 10:08 AM
requests and limits were correct, but my K3s Pod got slow anyway. The culprit wasn't OOMKill — it was cgroup v2's memory.high throttling early

#Kubernetes #DevOps #CloudNative
requests and limits were correct, but my K3s Pod got slow anyway. The culprit wasn't OOMKill — it was cgroup v2's memory.high throttling early
A K3s Pod with correctly configured requests/limits suddenly got slow, with no OOMKilled event anywhere. The real cause was cgroup v2's memory.high throttling. Here's how to diagnose and fix it.
kubo.hexabase.io
November 14, 2026 at 3:01 PM
JEP 523 matters particularly in small containers that previously selected Serial GC by default. Check CPU, RSS and pause times under the actual cgroup limits after upgrading. An explicit -XX:+UseZGC choice is separate from the default. openjdk.org/jeps/523
November 12, 2026 at 5:01 PM
For the GC part it is worth checking the new default under the actual container limits: small images that previously fell back to Serial now get G1, so compare CPU, RSS and pause times with the same cgroup limits after upgrading. openjdk.org/jeps/523
November 13, 2026 at 1:09 PM
Your shared host's noisy neighbor is why cached pages crawl at 400ms TTFB. A deep dive into Zone.eu benchmarks, cgroup limits, SSH control, and SLA fine print. #hosting #devops #infrastructure https://www.valtersit.com/guides/hosting/why-zone-eu-hosting/
Zone.eu Hosting Review: Affordable EU Infrastructure
www.valtersit.com
November 13, 2026 at 7:20 PM
PSI in /proc/pressure/memory and per-cgroup memory.pressure shows actual stall time, not just utilization. Read some/full with 10/60/300s averages to correlate memory pressure with real stalls. https://www.valtersit.com/vault/correlate-memory-pressure-with-psi-stall-time-on-cgroup-v2-e47083/
Correlate Memory Pressure with PSI Stall Time on cgroup v2
www.valtersit.com
November 10, 2026 at 7:30 AM
Der Singular beschreibt das komplette Feature und fungiert gleichzeitig als Bezeichner, wie bei den „cgroup controllers“.
https://docs.kernel.org/admin-guide/cgroup-v2.html
November 9, 2026 at 11:06 AM
requests and limits were correct, but my K3s Pod got slow anyway. The culprit wasn't OOMKill — it was cgroup v2's memory.high throttling early

#Kubernetes #DevOps #CloudNative
requests and limits were correct, but my K3s Pod got slow anyway. The culprit wasn't OOMKill — it was cgroup v2's memory.high throttling early
A K3s Pod with correctly configured requests/limits suddenly got slow, with no OOMKilled event anywhere. The real cause was cgroup v2's memory.high throttling. Here's how to diagnose and fix it.
kubo.hexabase.io
November 10, 2026 at 3:03 PM
Up to 10 AI agents, 30 GB of RAM, one queue: Sluice keeps their test runs out of each other's way, with a kernel memory ceiling per job and Chromium pulled back when it leaves its cgroup 🔍

https://josegarrido.dev/en/10-agents-30-gb-of-ram-and-a-queue/
10 agents, 30 GB of RAM and one queue: how they share without clashing
How Sluice lets up to 10 AI agents share one 30 GB Linux machine without clashing: one queue, kernel memory ceilings, and Chromium kept in its job.
josegarrido.dev
November 13, 2026 at 10:37 PM
🚨 EUVD-2025-5179
📊 n/a
🏢 Linux

📝 In the Linux kernel, the following vulnerability has been resolved:

blk-cgroup: Fix class @block_class's subsystem refcount leakage

blkcg_fill_root_iostats() i...

🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-5179

#cybersecurity #infosec #cve #euvd
November 10, 2026 at 1:05 PM
Kubernetes v1.35 starts failing kubelet startup on cgroup v1 nodes, pushing clusters to cgroup v2. 🐧⚙️🚀 #Kubernetes #Linux #cgroups #DevOps #PlatformEngineering
https://kubernetes.io/blog/2026/10/06/kubernetes-cgroups-v2-shift/
kubernetes.io
November 8, 2026 at 10:39 AM
Zennに記事を公開しました。Rootless Dockerでpwn環境の自動検証を安全にする話です。dockerグループ追加の代わりに専用rootlessデーモンを使い、DOCKER_HOSTの接続先とcgroup制限の実値を必ず確認する手順、実際に遭遇したglibc不一致の切り分けまでまとめました。https://zenn.dev/tasodoufu/articles/rootless-docker-safe-pwn-verification
November 10, 2026 at 10:55 AM
The cgroup v1 shutdown is the quiet kind of breaking change. One useful thought: monitor your node boot logs before the upgrade window, not after.
November 8, 2026 at 10:52 AM
i made my own ugly-as-fuck bar in quickshell and it's great because it only uses like 100M. this probably doesn't need that much memory though it's kind of egregious
November 8, 2026 at 7:43 PM
Your container was OOM-killed while ps showed only 300 MiB in use. Do you know why? Test yourself on Linux memory in cgroup v2.

The quiz is in this week's DevOpsLinks at https://faun.dev/picks/
November 9, 2026 at 2:00 PM
Understand how your Kubernetes CPU and memory limits actually work at the kernel level—from pod spec to cgroup enforcement in this deep-dive series.

https://www.reddit.com/r/kubernetes/comments/1xmmlaz/cgroups_a_deep_dive_into_resource_management_in/

#DevOps #platform
November 7, 2026 at 12:00 PM
📝 cgroup v2 memory.high Throttles, memory.max Kills: Measured on a Host Without Swap

We ran one allocating workload under memory.max, memory.high and both on a Linux 6.8 host with no swap. memory.max killed it in under half a second.

Read here: https://devops-daily.com/posts/cgroup-v2-memory-h...
devops-daily.com
November 6, 2026 at 4:00 PM
application file caches are out of scope, but if you mean memory then you can set per-cgroup memory limits, individually for causing the kernel to more aggressively reclaim within a cgroup, or to invoke OOM within a cgroup, or set a limit on how much swap it can use(including 0)
November 4, 2026 at 8:26 PM
systemd is kind of cool if you actually try to use it in good faith

for example, steam is downloading a bunch right now, and this is burning up this ones CPU.

but modern linux desktops and distros use systemd, and systemd puts apps in their own CGroup slices
November 4, 2026 at 8:05 PM