From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: Petr Holasek <pholasek@redhat.com>,
linux-kernel@vger.kernel.org, emunson@mgebm.net,
anton@redhat.com, Andi Kleen <ak@linux.intel.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Mel Gorman <mel@csn.ul.ie>, Wu Fengguang <fengguang.wu@intel.com>,
linux-mm@kvack.org
Subject: Re: [PATCH] hugetlb: /proc/meminfo shows data for all sizes of hugepages
Date: Mon, 7 Mar 2011 14:51:49 -0800 [thread overview]
Message-ID: <20110307145149.97e6676e.akpm@linux-foundation.org> (raw)
In-Reply-To: <1299527214.8493.13263.camel@nimitz>
On Mon, 07 Mar 2011 11:46:54 -0800
Dave Hansen <dave@linux.vnet.ibm.com> wrote:
> On Mon, 2011-03-07 at 14:05 +0100, Petr Holasek wrote:
> > + for_each_hstate(h)
> > + 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));
> > }
>
> It sounds like now we'll get a meminfo that looks like:
>
> ...
> AnonHugePages: 491520 kB
> HugePages_Total: 5
> HugePages_Free: 2
> HugePages_Rsvd: 3
> HugePages_Surp: 1
> Hugepagesize: 2048 kB
> HugePages_Total: 2
> HugePages_Free: 1
> HugePages_Rsvd: 1
> HugePages_Surp: 1
> Hugepagesize: 1048576 kB
> DirectMap4k: 12160 kB
> DirectMap2M: 2082816 kB
> DirectMap1G: 2097152 kB
>
> At best, that's a bit confusing. There aren't any other entries in
> meminfo that occur more than once. Plus, this information is available
> in the sysfs interface. Why isn't that sufficient?
>
> Could we do something where we keep the default hpage_size looking like
> it does now, but append the size explicitly for the new entries?
>
> HugePages_Total(1G): 2
> HugePages_Free(1G): 1
> HugePages_Rsvd(1G): 1
> HugePages_Surp(1G): 1
>
Let's not change the existing interface, please.
Adding new fields: OK.
Changing the way in whcih existing fields are calculated: OKish.
Renaming existing fields: not OK.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-03-07 22:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 13:05 [PATCH] hugetlb: /proc/meminfo shows data for all sizes of hugepages Petr Holasek
2011-03-07 19:46 ` Dave Hansen
2011-03-07 20:13 ` Eric B Munson
2011-03-07 22:51 ` Andrew Morton [this message]
2011-03-07 23:14 ` Naoya Horiguchi
2011-03-07 23:24 ` Eric B Munson
2011-03-07 23:25 ` Andrew Morton
2011-03-07 23:47 ` David Rientjes
2011-03-08 0:57 ` Nishanth Aravamudan
2011-03-08 9:37 ` Mel Gorman
2011-03-08 11:21 ` Petr Holasek
2011-03-08 13:51 ` Eric B Munson
2011-03-08 1:26 ` Andi Kleen
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=20110307145149.97e6676e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@linux.intel.com \
--cc=anton@redhat.com \
--cc=dave@linux.vnet.ibm.com \
--cc=emunson@mgebm.net \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=pholasek@redhat.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).