linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Roman Gushchin <guro@fb.com>
To: Muchun Song <songmuchun@bytedance.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
	Michal Hocko <mhocko@kernel.org>,
	Vladimir Davydov <vdavydov.dev@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Cgroups <cgroups@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [External] Re: [PATCH] mm/memcontrol: make the slab calculation consistent
Date: Wed, 2 Dec 2020 19:20:52 -0800	[thread overview]
Message-ID: <20201203032052.GA1568874@carbon.DHCP.thefacebook.com> (raw)
In-Reply-To: <CAMZfGtWUWAO8J6iBpQLV0T8xPAuQvFTfX9UQ7G2eM_O9C7w83w@mail.gmail.com>

On Thu, Dec 03, 2020 at 10:53:33AM +0800, Muchun Song wrote:
> On Thu, Dec 3, 2020 at 5:16 AM Roman Gushchin <guro@fb.com> wrote:
> >
> > On Wed, Dec 02, 2020 at 08:14:34PM +0800, Muchun Song wrote:
> > > Although the ratio of the slab is one, we also should read the ratio
> > > from the related memory_stats instead of hard-coding. And the local
> > > variable of size is already the value of slab_unreclaimable. So we
> > > do not need to read again. Simplify the code here.
> > >
> > > Signed-off-by: Muchun Song <songmuchun@bytedance.com>
> > > ---
> > >  mm/memcontrol.c | 22 +++++++++++++++++-----
> > >  1 file changed, 17 insertions(+), 5 deletions(-)
> >
> > Hi Muchun!
> >
> > >
> > > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > > index 9922f1510956..03a9c64560f6 100644
> > > --- a/mm/memcontrol.c
> > > +++ b/mm/memcontrol.c
> > > @@ -1545,12 +1545,22 @@ static int __init memory_stats_init(void)
> > >       int i;
> > >
> > >       for (i = 0; i < ARRAY_SIZE(memory_stats); i++) {
> > > +             switch (memory_stats[i].idx) {
> > >  #ifdef CONFIG_TRANSPARENT_HUGEPAGE
> > > -             if (memory_stats[i].idx == NR_ANON_THPS ||
> > > -                 memory_stats[i].idx == NR_FILE_THPS ||
> > > -                 memory_stats[i].idx == NR_SHMEM_THPS)
> > > +             case NR_ANON_THPS:
> > > +             case NR_FILE_THPS:
> > > +             case NR_SHMEM_THPS:
> > >                       memory_stats[i].ratio = HPAGE_PMD_SIZE;
> > > +                     break;
> > >  #endif
> > > +             case NR_SLAB_UNRECLAIMABLE_B:
> > > +                     VM_BUG_ON(i < 1);
> > > +                     VM_BUG_ON(memory_stats[i - 1].idx != NR_SLAB_RECLAIMABLE_B);
> >
> > Please, convert these to BUILD_BUG_ON(), they don't have to be runtime checks.
> 
> Agree. But here we cannot use BUILD_BUG_ON(). The compiler will
> complain about it.

We can!

We just need to change the condition. All we really need to check is that
NR_SLAB_UNRECLAIMABLE_B immediately following NR_SLAB_RECLAIMABLE_B.

Something like BUILD_BUG_ON(NR_SLAB_UNRECLAIMABLE_B != NR_SLAB_RECLAIMABLE_B + 1)
should work (completely untested).

> 
> >
> >
> > > +                     break;
> > > +             default:
> > > +                     break;
> > > +             }
> > > +
> > >               VM_BUG_ON(!memory_stats[i].ratio);
> > >               VM_BUG_ON(memory_stats[i].idx >= MEMCG_NR_STAT);
> > >       }
> > > @@ -1587,8 +1597,10 @@ static char *memory_stat_format(struct mem_cgroup *memcg)
> > >               seq_buf_printf(&s, "%s %llu\n", memory_stats[i].name, size);
> > >
> >
> > Can you, please, add a small comment here stating that we're printing
> > unreclaimable, reclaimable and the sum of both? It will simplify the reading of the code.
> 
> Will do.

Thank you!


  reply	other threads:[~2020-12-03  3:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 12:14 Muchun Song
2020-12-02 21:16 ` Roman Gushchin
2020-12-03  2:53   ` [External] " Muchun Song
2020-12-03  3:20     ` Roman Gushchin [this message]
2020-12-03  3:36       ` Muchun Song
2020-12-03  3:49         ` Roman Gushchin

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=20201203032052.GA1568874@carbon.DHCP.thefacebook.com \
    --to=guro@fb.com \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=songmuchun@bytedance.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