Re: [PATCH 1/2] memcg: expose vmpressure knobs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



No problem, since cgroups v1 are frozen that is a valid stopper.
Let me check what could be done about PSI for swapless cases.

On Tue, Apr 14, 2020 at 6:55 PM Chris Down <chris@xxxxxxxxxxxxxx> wrote:
svc_lmoiseichuk@xxxxxxxxxxxxx writes:
>From: Leonid Moiseichuk <lmoiseichuk@xxxxxxxxxxxxx>
>
>Populating memcg vmpressure controls with legacy defaults:
>- memory.pressure_window (512 or SWAP_CLUSTER_MAX * 16)
>- memory.pressure_level_critical_prio (3)
>- memory.pressure_level_medium (60)
>- memory.pressure_level_critical (95)
>
>Signed-off-by: Leonid Moiseichuk <lmoiseichuk@xxxxxxxxxxxxx>

I'm against this even in the abstract, cgroup v1 is deprecated and its
interface frozen, and vmpressure is pretty much already supplanted by PSI,
which actually works (whereas vmpressure often doesn't since it mostly ends up
just measuring reclaim efficiency, rather than actual memory pressure).

Without an extremely compelling reason to expose these, this just muddles the
situation.


--
With Best Wishes,
Leonid

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux