From: Dave Hansen <dave.hansen@intel.com>
To: Roman Gushchin <guro@fb.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.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>,
kernel-team@fb.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: show stats for non-default hugepage sizes in /proc/meminfo
Date: Mon, 13 Nov 2017 10:17:30 -0800 [thread overview]
Message-ID: <c716ac71-f467-dcbe-520f-91b007309a4d@intel.com> (raw)
In-Reply-To: <20171113181105.GA27034@castle>
On 11/13/2017 10:11 AM, Roman Gushchin wrote:
> On Mon, Nov 13, 2017 at 09:06:32AM -0800, Dave Hansen wrote:
>> On 11/13/2017 08:03 AM, Roman Gushchin wrote:
>>> To solve this problem, let's display stats for all hugepage sizes.
>>> To provide the backward compatibility let's save the existing format
>>> for the default size, and add a prefix (e.g. 1G_) for non-default sizes.
>>
>> Is there something keeping you from using the sysfs version of this
>> information?
>
> Just answered the same question to Michal.
>
> In two words: it would be nice to have a high-level overview of
> memory usage in the system in /proc/meminfo.
I don't think it's worth cluttering up meminfo for this, imnho.
--
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-13 18:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 16:03 Roman Gushchin
2017-11-13 16:11 ` Michal Hocko
2017-11-13 16:33 ` Roman Gushchin
2017-11-14 8:21 ` Michal Hocko
2017-11-13 17:06 ` Dave Hansen
2017-11-13 18:11 ` Roman Gushchin
2017-11-13 18:17 ` Dave Hansen [this message]
2017-11-13 18:30 ` Mike Kravetz
2017-11-13 18:45 ` Roman Gushchin
2017-11-13 19:10 ` Johannes Weiner
2017-11-13 19:25 ` Mike Kravetz
2017-11-14 12:48 ` Roman Gushchin
2017-11-13 19:31 ` 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=c716ac71-f467-dcbe-520f-91b007309a4d@intel.com \
--to=dave.hansen@intel.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.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 \
/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