Re: [PATCH 00/11] mm/cma: charge cma allocation to memcg using per area counters
Michal Koutný <[email protected]>
| Newsgroups | org.kernel.vger.linux-doc,org.kernel.vger.cgroups,org.kernel.vger.linux-kernel,org.kernel.vger.linux-kselftest,org.kvack.linux-mm |
|---|---|
| Message-ID | <[email protected]> |
Hi Eric. On Fri, Aug 21, 2026 at 02:56:52PM -0400, Eric Chanudet <[email protected]> wrote: > Finally register the per-area usage counters in the cgroupfs. Each CMA > area creates a memory.cma.<area>.{current,max} pair for reporting and > limitation for each area. These areas quite resemble dmem regions. What is the relation to the previous dmem double-charging [1]? (Successor, alternative,...) Thanks, Michal
signature.asc
(application/pgp-signature, 265 B)
-----BEGIN PGP SIGNATURE----- iJEEABYKADkWIQRCE24Fn/AcRjnLivR+PQLnlNv4CAUCaoxEuhsUgAAAAAAEAA5t YW51MiwyLjUrMS4xMiwyLDIACgkQfj0C55Tb+Ai6WwEAt6IhJ1j5eKMrYIQuXx6H vcVhIKJYy4uCLIiKXOf6/zMA/jVVm1UxH8BKR0Myu49nuRzoWqbLCU9ie1WLGOPG nZIA =+xTm -----END PGP SIGNATURE-----