Re: Path forward for Virtualized Swap?

[Rik van Riel <riel@surriel.com>]

On Sat, 2026-09-19 at 11:21 -1000, Chris Li wrote:
> On Sat, Sep 19, 2026 at 6:16 AM Rik van Riel <riel@surriel.com>
> wrote:
> > 
> 
> > However, I believe we do need to take care that
> > whatever design we go with is actually able to
> > support the end user functionality we want.
> 
> Agree. I want to add that we should support new functionality without
> sacrificing existing user functionality.
> 
That means things need to work both for users
who want to configure a zswap size, and for
those who do not.

The cgroup memory.swap.max is an existing
interface that does that on a per cgroup
basis for swap, though in practice the 
limit mostly seems to be set to 0 (no swap),
or to max (no limit).

memory.zswap.max does the same on the zswap
side, again mostly 0 or max are used.

Are you saying you rely on having something
like that at the system level, too?

-- 
All Rights Reversed.