On Mon, Aug 24, 2026 at 03:18:54PM +0200, Michal Koutný wrote: > 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,...)
They are, although I did not make it clear in the cover letter, my bad. This is a CMA centric alternative to the other series that tried to issue the memcg charge through dmem[1]. CMA seemed to better fit under memcg directly as I couldn't find a solution on how to correctly charge memcg once in dmem where it was determined to double-charge or not. [1] https://lore.kernel.org/all/20260519-cgroup-dmem-memcg-double-charge-v2-0-db4d14070...@redhat.com/ > > Thanks, > Michal -- Eric Chanudet
