From: Johannes Weiner <hannes@cmpxchg.org>
To: Hao Jia <jiahao.kernel@gmail.com>
Cc: akpm@linux-foundation.org, tj@kernel.org, corbet@lwn.net,
mhocko@kernel.org, roman.gushchin@linux.dev,
shakeel.butt@linux.dev, muchun.song@linux.dev, mkoutny@suse.com,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Hao Jia <jiahao1@lixiang.com>
Subject: Re: [PATCH 1/2] mm: vmscan: Split proactive reclaim statistics from direct reclaim statistics
Date: Tue, 18 Mar 2025 12:42:43 -0400 [thread overview]
Message-ID: <20250318164243.GA1867495@cmpxchg.org> (raw)
In-Reply-To: <20250318075833.90615-2-jiahao.kernel@gmail.com>
On Tue, Mar 18, 2025 at 03:58:32PM +0800, Hao Jia wrote:
> From: Hao Jia <jiahao1@lixiang.com>
>
> In proactive memory reclaim scenarios, it is necessary to
> accurately track proactive reclaim statistics to dynamically
> adjust the frequency and amount of memory being reclaimed
> proactively. Currently, proactive reclaim is included in
> direct reclaim statistics, which can make these
> direct reclaim statistics misleading.
>
> Therefore, separate proactive reclaim memory from the
> direct reclaim counters by introducing new counters:
> pgsteal_proactive, pgdemote_proactive, and pgscan_proactive,
> to avoid confusion with direct reclaim.
>
> Signed-off-by: Hao Jia <jiahao1@lixiang.com>
This is indeed quite useful.
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
next prev parent reply other threads:[~2025-03-18 16:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 7:58 [PATCH 0/2] Adding Proactive Memory Reclaim Statistics Hao Jia
2025-03-18 7:58 ` [PATCH 1/2] mm: vmscan: Split proactive reclaim statistics from direct reclaim statistics Hao Jia
2025-03-18 10:17 ` Michal Koutný
2025-03-18 12:03 ` Hao Jia
2025-03-18 12:59 ` Michal Koutný
2025-03-19 2:38 ` Hao Jia
2025-03-19 9:15 ` Michal Koutný
2025-03-19 9:49 ` Hao Jia
2025-03-19 10:33 ` Michal Koutný
2025-03-19 15:44 ` Johannes Weiner
2025-03-21 12:30 ` Michal Koutný
2025-03-18 16:42 ` Johannes Weiner [this message]
2025-03-18 7:58 ` [PATCH 2/2] cgroup: docs: Add pswpin and pswpout items in cgroup v2 doc Hao Jia
2025-03-18 10:18 ` Michal Koutný
2025-03-18 15:58 ` Tejun Heo
2025-03-18 16:43 ` Johannes Weiner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250318164243.GA1867495@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=jiahao.kernel@gmail.com \
--cc=jiahao1@lixiang.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mkoutny@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.