Just like we have memory.peak, introduce a dmem.peak, which uses the page_counter support for that.
It can be written to in order to reset the peak, but different from memory.peak, which expects any write, dmem.peak expects the region name to be written to it. That region peak is the one that is reset. That requires ofp_peak to carry a pointer to the pool that was reset. Writing a different region name will reset the different region and make the original region peak get back to its non-reset value. While at it, we reuse a helper from memcontrol, which we moved to kernel/cgroup/cgroup.c. Signed-off-by: Thadeu Lima de Souza Cascardo <[email protected]> --- Thadeu Lima de Souza Cascardo (2): mm/page_counter: decouple peak_reset from peak_write cgroup/dmem: introduce a peak file Documentation/admin-guide/cgroup-v2.rst | 10 +++ include/linux/cgroup-defs.h | 7 ++ kernel/cgroup/cgroup.c | 32 ++++++++ kernel/cgroup/dmem.c | 132 ++++++++++++++++++++++++++++++-- mm/memcontrol.c | 42 ++-------- 5 files changed, 183 insertions(+), 40 deletions(-) --- base-commit: 7fd2df204f342fc17d1a0bfcd474b24232fb0f32 change-id: 20260409-dmem_peak-3abc1be95072 Best regards, -- Thadeu Lima de Souza Cascardo <[email protected]>
