From: Hao Jia <jiahao.kernel@gmail.com>
To: hannes@cmpxchg.org, 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
Cc: cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Hao Jia <jiahao1@lixiang.com>
Subject: [PATCH 0/2] Adding Proactive Memory Reclaim Statistics
Date: Tue, 18 Mar 2025 15:58:31 +0800 [thread overview]
Message-ID: <20250318075833.90615-1-jiahao.kernel@gmail.com> (raw)
From: Hao Jia <jiahao1@lixiang.com>
These two patches are related to proactive memory reclaim.
Patch 1 Split proactive reclaim statistics from direct reclaim counters
and introduces new counters: pgsteal_proactive, pgdemote_proactive,
and pgscan_proactive.
Patch 2 Adds pswpin and pswpout items to the cgroup-v2 documentation.
Hao Jia (2):
mm: vmscan: Split proactive reclaim statistics from direct reclaim
statistics
cgroup, docs: Add pswpin and pswpout items in cgroup v2 doc
Documentation/admin-guide/cgroup-v2.rst | 15 +++++++++++
include/linux/mmzone.h | 1 +
include/linux/vm_event_item.h | 2 ++
mm/memcontrol.c | 7 +++++
mm/vmscan.c | 35 ++++++++++++++-----------
mm/vmstat.c | 3 +++
6 files changed, 48 insertions(+), 15 deletions(-)
--
2.34.1
next reply other threads:[~2025-03-18 7:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 7:58 Hao Jia [this message]
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
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=20250318075833.90615-1-jiahao.kernel@gmail.com \
--to=jiahao.kernel@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox