From: Michal Hocko <mhocko@suse.com>
To: Chuyi Zhou <zhouchuyi@bytedance.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, 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 15:55:49 +0200 [thread overview]
Message-ID: <Ys19ZasxrKQsedtj@dhcp22.suse.cz> (raw)
In-Reply-To: <333e16e8-95a8-20e4-6be4-4cc3a602c7b2@bytedance.com>
On Tue 12-07-22 17:28:50, Chuyi Zhou wrote:
>
>
> 在 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 ?
We already do have events for that - have a look MEMCG_MAX. Can you work
with that?
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2022-07-12 13:55 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
2022-07-12 13:55 ` Michal Hocko [this message]
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=Ys19ZasxrKQsedtj@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=songmuchun@bytedance.com \
--cc=zhouchuyi@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