linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Roman Gushchin <guro@fb.com>
Cc: linux-mm@kvack.org, Michal Hocko <mhocko@suse.com>,
	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>,
	David Rientjes <rientjes@google.com>,
	kernel-team@fb.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm: show total hugetlb memory consumption in /proc/meminfo
Date: Mon, 20 Nov 2017 16:51:10 -0800	[thread overview]
Message-ID: <20171120165110.587918bf75ffecb8144da66c@linux-foundation.org> (raw)
In-Reply-To: <20171115231409.12131-1-guro@fb.com>

On Wed, 15 Nov 2017 23:14:09 +0000 Roman Gushchin <guro@fb.com> wrote:

> Currently we display some hugepage statistics (total, free, etc)
> in /proc/meminfo, but only for default hugepage size (e.g. 2Mb).
> 
> If hugepages of different sizes are used (like 2Mb and 1Gb on x86-64),
> /proc/meminfo output can be confusing, as non-default sized hugepages
> are not reflected at all, and there are no signs that they are
> existing and consuming system memory.
> 
> To solve this problem, let's display the total amount of memory,
> consumed by hugetlb pages of all sized (both free and used).
> Let's call it "Hugetlb", and display size in kB to match generic
> /proc/meminfo style.
> 
> For example, (1024 2Mb pages and 2 1Gb pages are pre-allocated):
>   $ cat /proc/meminfo
>   MemTotal:        8168984 kB
>   MemFree:         3789276 kB
>   <...>
>   CmaFree:               0 kB
>   HugePages_Total:    1024
>   HugePages_Free:     1024
>   HugePages_Rsvd:        0
>   HugePages_Surp:        0
>   Hugepagesize:       2048 kB
>   Hugetlb:         4194304 kB
>   DirectMap4k:       32632 kB
>   DirectMap2M:     4161536 kB
>   DirectMap1G:     6291456 kB
> 
> Also, this patch updates corresponding docs to reflect
> Hugetlb entry meaning and difference between Hugetlb and
> HugePages_Total * Hugepagesize.
> 
> ...
>
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -2973,20 +2973,32 @@ int hugetlb_overcommit_handler(struct ctl_table *table, int write,
>  
>  void hugetlb_report_meminfo(struct seq_file *m)
>  {
> -	struct hstate *h = &default_hstate;
> +	struct hstate *h;
> +	unsigned long total = 0;
> +
>  	if (!hugepages_supported())
>  		return;
> -	seq_printf(m,
> -			"HugePages_Total:   %5lu\n"
> -			"HugePages_Free:    %5lu\n"
> -			"HugePages_Rsvd:    %5lu\n"
> -			"HugePages_Surp:    %5lu\n"
> -			"Hugepagesize:   %8lu kB\n",
> -			h->nr_huge_pages,
> -			h->free_huge_pages,
> -			h->resv_huge_pages,
> -			h->surplus_huge_pages,
> -			1UL << (huge_page_order(h) + PAGE_SHIFT - 10));
> +
> +	for_each_hstate(h) {
> +		unsigned long count = h->nr_huge_pages;
> +
> +		total += (PAGE_SIZE << huge_page_order(h)) * count;
> +
> +		if (h == &default_hstate)

I'm not understanding this test.  Are we assuming that default_hstate
always refers to the highest-index hstate?  If so why, and is that
valid?

> +			seq_printf(m,
> +				   "HugePages_Total:   %5lu\n"
> +				   "HugePages_Free:    %5lu\n"
> +				   "HugePages_Rsvd:    %5lu\n"
> +				   "HugePages_Surp:    %5lu\n"
> +				   "Hugepagesize:   %8lu kB\n",
> +				   count,
> +				   h->free_huge_pages,
> +				   h->resv_huge_pages,
> +				   h->surplus_huge_pages,
> +				   (PAGE_SIZE << huge_page_order(h)) / 1024);
> +	}
> +
> +	seq_printf(m, "Hugetlb:        %8lu kB\n", total / 1024);
>  }

--
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>

  parent reply	other threads:[~2017-11-21  0:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 23:14 [PATCH v2] mm: show total hugetlb memory consumption in /proc/meminfo Roman Gushchin
2017-11-16  9:11 ` Michal Hocko
2017-11-16 14:22 ` Johannes Weiner
2017-11-17  9:41 ` David Rientjes
2017-11-21  0:51 ` Andrew Morton [this message]
2017-11-21  1:09   ` Mike Kravetz
2017-11-21  7:01   ` Michal Hocko
2017-11-21 15:15   ` Roman Gushchin
2017-11-21 19:19     ` Andrew Morton
2017-11-21 19:59       ` Roman Gushchin
2017-11-22  0:27         ` Mike Kravetz
2017-11-22  9:10           ` 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=20171120165110.587918bf75ffecb8144da66c@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aarcange@redhat.com \
    --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=mhocko@suse.com \
    --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;
as well as URLs for NNTP newsgroup(s).