Re: Path forward for Virtualized Swap?

[Rik van Riel]

On Sat, 2026-09-19 at 09:02 -1000, Chris Li wrote:
> 
> Secondly, I notice that you are reasoning from the memory usage
> aspect. That is a different usage requirement angle than the SLO
> violations. Maybe we need a separate counter to track actual memory
> usage, regardless of compression status.
> 
That's what the cgroup memory.current does.

It adds up anonymous, file, accounted slab, and
(after compression) zswap memory use for a cgroup,
and can be limited with all the usual cgroup
limits.

-- 
All Rights Reversed.