[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240916004134.0ef2f50862b59079e1ac2928@linux-foundation.org>
Date: Mon, 16 Sep 2024 00:41:34 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Jingxiang Zeng <jingxiangzeng.cas@...il.com>
Cc: linux-mm@...ck.org, cgroups@...r.kernel.org, hannes@...xchg.org,
linuszeng@...cent.com, linux-kernel@...r.kernel.org, mhocko@...nel.org,
muchun.song@...ux.dev, roman.gushchin@...ux.dev, shakeel.butt@...ux.dev,
yosryahmed@...gle.com
Subject: Re: [PATCH V2] mm/memcontrol: add per-memcg pgpgin/pswpin counter
On Fri, 13 Sep 2024 16:44:53 +0800 Jingxiang Zeng <jingxiangzeng.cas@...il.com> wrote:
> From: Jingxiang Zeng <linuszeng@...cent.com>
>
> In proactive memory reclamation scenarios, it is necessary to estimate the
> pswpin and pswpout metrics of the cgroup to determine whether to continue
> reclaiming anonymous pages in the current batch. This patch will collect
> these metrics and expose them.
>
Please explain the differences between v1 and v2:
--- a/mm/memcontrol-v1.c~mm-memcontrol-add-per-memcg-pgpgin-pswpin-counter-v2
+++ a/mm/memcontrol-v1.c
@@ -2729,8 +2729,6 @@ static const char *const memcg1_stat_nam
static const unsigned int memcg1_events[] = {
PGPGIN,
PGPGOUT,
- PSWPIN,
- PSWPOUT,
PGFAULT,
PGMAJFAULT,
};
_
Powered by blists - more mailing lists