From: Chuyi Zhou <zhouchuyi@bytedance.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, Michal Hocko <mhocko@suse.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Johannes Weiner <hannes@cmpxchg.org>,
Shakeel Butt <shakeelb@google.com>,
Muchun Song <songmuchun@bytedance.com>
Subject: Re: [PATCH] mm/vmscan: add pgstall to memcg
Date: Tue, 12 Jul 2022 17:28:50 +0800 [thread overview]
Message-ID: <333e16e8-95a8-20e4-6be4-4cc3a602c7b2@bytedance.com> (raw)
In-Reply-To: <20220624134218.e25104d902f7fde209728a23@linux-foundation.org>
在 2022/6/25 上午4:42, Andrew Morton 写道:
> (cc memcg developers)
> On Thu, 23 Jun 2022 16:01:03 +0800 zhouchuyi <zhouchuyi@bytedance.com> wrote:
>
>> Add pgstall to indicate the times of entering direct reclaim of memcg, use
>> the item of ALLOCSTALL_NORMAL in vmevents to save the data.
>>
>> Signed-off-by: zhouchuyi <zhouchuyi@bytedance.com>
>> ---
>>
>>
>> Hi,
>>
>> I notice memcg uses some items to indicate the situation of direct reclaim in memory.stat,such as pgsteal and pgscan.
>> I think there is no harm in adding another item to show the times of entering direct reclaim.
>>
>
> Why do you consider this useful? Do you have a use case? If so,
> please describe it in detail.
>
Since there are allocstall in proc/vmstat which indicate the number of
entering direct reclaim of !cgroup_reclaim, So I think it maybe useful.
For example, users could adjust memory.max to prevent entering direct
reclaim through this item.So what do you think about it ?
>>
>> ...
>>
>> diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst
>> index 176298f2f..44c5b15bd 100644
>> --- a/Documentation/admin-guide/cgroup-v2.rst
>> +++ b/Documentation/admin-guide/cgroup-v2.rst
>> @@ -1447,8 +1447,11 @@ PAGE_SIZE multiple when read back.
>>
>> pgsteal (npn)
>> Amount of reclaimed pages
>> -
>> - pgactivate (npn)
>> +
>> + pgstall (npn)
>> + Number of entering direct reclaim
>> +
>> + pgactivate (npn)
>> Amount of pages moved to the active LRU list
>>
>> pgdeactivate (npn)
>> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
>> index abec50f31..f407084b2 100644
>> --- a/mm/memcontrol.c
>> +++ b/mm/memcontrol.c
>> @@ -1505,6 +1505,8 @@ static char *memory_stat_format(struct mem_cgroup *memcg)
>> seq_buf_printf(&s, "pgscan %lu\n",
>> memcg_events(memcg, PGSCAN_KSWAPD) +
>> memcg_events(memcg, PGSCAN_DIRECT));
>> + seq_buf_printf(&s, "pgstall %lu\n",
>> + memcg_events(memcg, ALLOCSTALL_NORMAL));
>> seq_buf_printf(&s, "pgsteal %lu\n",
>> memcg_events(memcg, PGSTEAL_KSWAPD) +
>> memcg_events(memcg, PGSTEAL_DIRECT));
>> diff --git a/mm/vmscan.c b/mm/vmscan.c
>> index f7d9a683e..107cec59a 100644
>> --- a/mm/vmscan.c
>> +++ b/mm/vmscan.c
>> @@ -3532,7 +3532,10 @@ static unsigned long do_try_to_free_pages(struct zonelist *zonelist,
>>
>> if (!cgroup_reclaim(sc))
>> __count_zid_vm_events(ALLOCSTALL, sc->reclaim_idx, 1);
>> -
>> + else {
>> + count_memcg_events(sc->target_mem_cgroup,
>> + ALLOCSTALL_NORMAL, 1);
>> + }
>> do {
>> vmpressure_prio(sc->gfp_mask, sc->target_mem_cgroup,
>> sc->priority);
>> --
>> 2.20.1
next prev parent reply other threads:[~2022-07-12 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 8:01 zhouchuyi
2022-06-24 20:42 ` Andrew Morton
2022-07-12 9:28 ` Chuyi Zhou [this message]
2022-07-12 13:55 ` Michal Hocko
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=333e16e8-95a8-20e4-6be4-4cc3a602c7b2@bytedance.com \
--to=zhouchuyi@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=songmuchun@bytedance.com \
/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