From: Michal Hocko <mhocko@kernel.org>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Chris Down <chris@chrisdown.name>,
Andrew Morton <akpm@linux-foundation.org>,
Cgroups <cgroups@vger.kernel.org>, Linux MM <linux-mm@kvack.org>,
shaoyafang@didiglobal.com
Subject: Re: [PATCH] mm/memcg: add allocstall to memory.stat
Date: Fri, 12 Apr 2019 08:34:17 +0200 [thread overview]
Message-ID: <20190412063417.GA13373@dhcp22.suse.cz> (raw)
In-Reply-To: <CALOAHbBCGx-d-=Z0CdL+tzWRCCQ7Hd9CFqjMhLKbEofDfFpoMw@mail.gmail.com>
On Fri 12-04-19 09:32:55, Yafang Shao wrote:
> On Thu, Apr 11, 2019 at 11:10 PM Michal Hocko <mhocko@kernel.org> wrote:
> >
> > On Thu 11-04-19 21:54:22, Yafang Shao wrote:
> > > On Thu, Apr 11, 2019 at 9:39 PM Michal Hocko <mhocko@kernel.org> wrote:
> > > >
> > > > On Thu 11-04-19 20:41:32, Yafang Shao wrote:
> > > > > On Thu, Apr 11, 2019 at 8:27 PM Michal Hocko <mhocko@kernel.org> wrote:
> > > > > >
> > > > > > On Thu 11-04-19 19:59:51, Yafang Shao wrote:
> > > > > > > The current item 'pgscan' is for pages in the memcg,
> > > > > > > which indicates how many pages owned by this memcg are scanned.
> > > > > > > While these pages may not scanned by the taskes in this memcg, even for
> > > > > > > PGSCAN_DIRECT.
> > > > > > >
> > > > > > > Sometimes we need an item to indicate whehter the tasks in this memcg
> > > > > > > under memory pressure or not.
> > > > > > > So this new item allocstall is added into memory.stat.
> > > > > >
> > > > > > We do have memcg events for that purpose and those can even tell whether
> > > > > > the pressure is a result of high or hard limit. Why is this not
> > > > > > sufficient?
> > > > > >
> > > > >
> > > > > The MEMCG_HIGH and MEMCG_LOW may not be tiggered by the tasks in this
> > > > > memcg neither.
> > > > > They all reflect the memory status of a memcg, rather than tasks
> > > > > activity in this memcg.
> > > >
> > > > I do not follow. Can you give me an example when does this matter? I
> > >
> > > For example, the tasks in this memcg may encounter direct page reclaim
> > > due to system memory pressure,
> > > meaning it is stalling in page alloc slow path.
> > > At the same time, maybe there's no memory pressure in this memcg, I
> > > mean, it could succussfully charge memcg.
> >
> > And that is exactly what those events aim for. They are measuring
> > _where_ the memory pressure comes from.
> >
> > Can you please try to explain what do you want to achieve again?
>
> To know the impact of this memory pressure.
> The current events can tell us the source of this pressure, but can't
> tell us the impact of this pressure.
Can you give me a more specific example how you are going to use this
counter in a real life please?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-04-12 6:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 11:59 [PATCH] mm/memcg: add allocstall to memory.stat Yafang Shao
2019-04-11 12:26 ` Michal Hocko
2019-04-11 12:41 ` Yafang Shao
2019-04-11 13:39 ` Michal Hocko
2019-04-11 13:54 ` Yafang Shao
2019-04-11 15:10 ` Michal Hocko
2019-04-12 1:32 ` Yafang Shao
2019-04-12 6:34 ` Michal Hocko [this message]
2019-04-12 8:10 ` Yafang Shao
2019-04-12 9:09 ` Michal Hocko
2019-04-12 9:29 ` Yafang Shao
2019-04-12 9:36 ` Michal Hocko
2019-04-12 9:48 ` Yafang Shao
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=20190412063417.GA13373@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chris@chrisdown.name \
--cc=hannes@cmpxchg.org \
--cc=laoar.shao@gmail.com \
--cc=linux-mm@kvack.org \
--cc=shaoyafang@didiglobal.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;
as well as URLs for NNTP newsgroup(s).