From: Michal Hocko <mhocko@kernel.org>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux MM <linux-mm@kvack.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Yafang Shao <shaoyafang@didiglobal.com>
Subject: Re: [PATCH v2] mm/memcontrol: keep local VM counters in sync with the hierarchical ones
Date: Fri, 12 Jul 2019 07:29:38 +0200 [thread overview]
Message-ID: <20190712052938.GI29483@dhcp22.suse.cz> (raw)
In-Reply-To: <CALOAHbDC+JWaXfMwG97PEsEB4f0vRkx7JsDRN8m47x1DMVuuFg@mail.gmail.com>
On Fri 12-07-19 09:47:14, Yafang Shao wrote:
> On Fri, Jul 12, 2019 at 7:42 AM Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > On Thu, 11 Jul 2019 09:32:59 -0400 Yafang Shao <laoar.shao@gmail.com> wrote:
> >
> > > After commit 815744d75152 ("mm: memcontrol: don't batch updates of local VM stats and events"),
> > > the local VM counters is not in sync with the hierarchical ones.
> > >
> > > Bellow is one example in a leaf memcg on my server (with 8 CPUs),
> > > inactive_file 3567570944
> > > total_inactive_file 3568029696
> > > We can find that the deviation is very great, that is because the 'val' in
> > > __mod_memcg_state() is in pages while the effective value in
> > > memcg_stat_show() is in bytes.
> > > So the maximum of this deviation between local VM stats and total VM
> > > stats can be (32 * number_of_cpu * PAGE_SIZE), that may be an unacceptable
> > > great value.
> > >
> > > We should keep the local VM stats in sync with the total stats.
> > > In order to keep this behavior the same across counters, this patch updates
> > > __mod_lruvec_state() and __count_memcg_events() as well.
> >
> > hm.
> >
> > So the local counters are presently more accurate than the hierarchical
> > ones because the hierarchical counters use batching. And the proposal
> > is to make the local counters less accurate so that the inaccuracies
> > will match.
> >
> > It is a bit counter intuitive to hear than worsened accuracy is a good
> > thing! We're told that the difference may be "unacceptably great" but
> > we aren't told why. Some additional information to support this
> > surprising assertion would be useful, please. What are the use-cases
> > which are harmed by this difference and how are they harmed?
> >
>
> Hi Andrew,
>
> Both local counter and the hierachical one are exposed to user.
> In a leaf memcg, the local counter should be equal with the hierarchical one,
> if they are different, the user may wondering what's wrong in this memcg.
> IOW, the difference makes these counters not reliable, if they are not
> reliable we can't use them to help us anylze issues.
But those numbers are in flight anyway. We do not stop updating them
while they are read so there is no guarantee they will be consistent
anyway, right?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-07-12 5:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 13:32 Yafang Shao
2019-07-11 15:19 ` Johannes Weiner
2019-07-11 23:42 ` Andrew Morton
2019-07-12 1:47 ` Yafang Shao
2019-07-12 5:29 ` Michal Hocko [this message]
2019-07-12 6:12 ` Yafang Shao
2019-07-12 6:53 ` Michal Hocko
2019-07-12 7:14 ` Yafang Shao
2019-07-12 7:54 ` 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=20190712052938.GI29483@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=laoar.shao@gmail.com \
--cc=linux-mm@kvack.org \
--cc=shaoyafang@didiglobal.com \
--cc=vdavydov.dev@gmail.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