From: Michal Hocko <mhocko@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: Roman Gushchin <guro@fb.com>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Dave Hansen <dave.hansen@intel.com>,
kernel-team@fb.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: show total hugetlb memory consumption in /proc/meminfo
Date: Wed, 15 Nov 2017 09:18:18 +0100 [thread overview]
Message-ID: <20171115081818.ucnp26tho4qffdwx@dhcp22.suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.10.1711141425220.112995@chino.kir.corp.google.com>
On Tue 14-11-17 14:28:11, David Rientjes wrote:
[...]
> > /proc/meminfo is paved with mistakes throughout the history. It pretends
> > to give a good picture of the memory usage, yet we have many pointless
> > entries while large consumers are not reflected at all in many case.
> >
> > Hugetlb data with that great details shouldn't have been exported in the
> > first place when they reflect only one specific hugepage size. I would
> > argue that if somebody went down to configure non-default hugetlb page
> > sizes then checking for the sysfs stats would be an immediate place to
> > look at. Anyway I can see that the cumulative information might be
> > helpful for those who do not own the machine but merely debug an issue
> > which is the primary usacase for the file.
> >
>
> I agree in principle, but I think it's inevitable on projects that span
> decades and accumulate features that evolve over time.
Yes, this is acceptable in earlier stages but I believe we have reached
a mature state where we shouldn't repeat those mistakes.
[...]
> > > if (!hugepages_supported())
> > > return;
> > > seq_printf(m,
> > > @@ -2987,6 +2989,11 @@ void hugetlb_report_meminfo(struct seq_file *m)
> > > h->resv_huge_pages,
> > > h->surplus_huge_pages,
> > > 1UL << (huge_page_order(h) + PAGE_SHIFT - 10));
> > > +
> > > + for_each_hstate(h)
> > > + total += (PAGE_SIZE << huge_page_order(h)) * h->nr_huge_pages;
> >
> > Please keep the total calculation consistent with what we have there
> > already.
> >
>
> Yeah, and I'm not sure if your comment eludes to this being racy, but it
> would be better to store the default size for default_hstate during the
> iteration to total the size for all hstates.
I just meant to have the code consistent. I do not prefer one or other
option.
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-11-15 8:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 12:50 Roman Gushchin
2017-11-14 13:17 ` Michal Hocko
2017-11-14 22:28 ` David Rientjes
2017-11-15 8:18 ` Michal Hocko [this message]
2017-11-15 22:46 ` David Rientjes
2017-11-15 22:49 ` Roman Gushchin
2017-11-14 21:07 ` Johannes Weiner
2017-11-14 21:10 ` Dave Hansen
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=20171115081818.ucnp26tho4qffdwx@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dave.hansen@intel.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=rientjes@google.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