---
title: "Discussion on \"Memory Cgroup: Charge Coalescing using Per-CPU Memcg Stock (v2.6.33)\" | Hashnode"
description: "Discussion on \"Memory Cgroup: Charge Coalescing using Per-CPU Memcg Stock (v2.6.33)\". Intro\nBy nature, memory cgroup charging can lead to significant lock contention on the spinlock of struct res_counter when processes in a memory cgroup run on multiple CPUs. This happens because the kernel maintains a struct res_counter for each memo..."
url: "https://hashnode.com/posts/memory-cgroup-charge-coalescing-using-per-cpu-memcg-stock-v2633/684f215cca8d2fd75036094a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Memory Cgroup: Charge Coalescing using Per-CPU Memcg Stock (v2.6.33)](https://vmscan.org/memory-cgroup-charge-coalescing-using-per-cpu-memcg-stock-v2633?utm_source=hashnode&utm_medium=feed)

Intro By nature, memory cgroup charging can lead to significant lock contention on the spinlock of struct res\_counter when processes in a memory cgroup run on multiple CPUs. This happens because the kernel maintains a struct res\_counter for each memo...

Jun 15, 2025 · 11 min read · vmscan.org  
Read the article

-   [#memcg](https://hashnode.com/tag/memcg)
-   [#linux-kernel](https://hashnode.com/tag/linux-kernel)
-   [#memory-management](https://hashnode.com/tag/memory-management)
-   [#cgroups](https://hashnode.com/tag/cgroups)

## Written by

[Harry Yoo](https://hashnode.com/@hyeyoo)

@hyeyoo

  
[View profile](https://hashnode.com/@hyeyoo)

Endless Learning

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
