From: "Michal Koutný" <mkoutny@suse.com>
To: Hao Jia <jiahao1@lixiang.com>
Cc: Hao Jia <jiahao.kernel@gmail.com>,
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,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/2] mm: vmscan: Split proactive reclaim statistics from direct reclaim statistics
Date: Wed, 19 Mar 2025 11:33:10 +0100 [thread overview]
Message-ID: <rxgfvctb5a5plo2o54uegyocmofdcxfxfwwjsn2lrgazdxxbnc@b4xdyfsuplwd> (raw)
In-Reply-To: <3a7a14fb-2eb7-3580-30f8-9a8f1f62aad4@lixiang.com>
[-- Attachment #1: Type: text/plain, Size: 678 bytes --]
On Wed, Mar 19, 2025 at 05:49:15PM +0800, Hao Jia <jiahao1@lixiang.com> wrote:
> root
> `- a `- b`- c
>
> We have a userspace proactive memory reclaim process that writes to
> a/memory.reclaim, observes a/memory.stat, then writes to
> b/memory.reclaim and observes b/memory.stat. This pattern is the same
> for other cgroups as well, so all memory cgroups(a, b, c) have the
> **same writer**. So, I need per-cgroup proactive memory reclaim statistics.
Sorry for unclarity, it got lost among the mails. Originally, I thought
about each write(2) but in reality it'd be per each FD. Similar to how
memory.peak allows seeing different values. WDYT?
Michal
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-03-19 10:33 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ý [this message]
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=rxgfvctb5a5plo2o54uegyocmofdcxfxfwwjsn2lrgazdxxbnc@b4xdyfsuplwd \
--to=mkoutny@suse.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--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=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