From: Dave Hansen <dave.hansen@intel.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Thelen <gthelen@google.com>,
David Rientjes <rientjes@google.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Dan Williams <dan.j.williams@intel.com>, Jan Kara <jack@suse.cz>,
linux-mm@kvack.org
Subject: Re: [PATCH] mm: make transparent hugepage size public
Date: Tue, 6 Dec 2016 11:27:28 -0800 [thread overview]
Message-ID: <db569a60-5dd1-b0a8-9fcb-6dd2106765ee@intel.com> (raw)
In-Reply-To: <20161206171905.n7qwvfb5sjxn3iif@black.fi.intel.com>
On 12/06/2016 09:19 AM, Kirill A. Shutemov wrote:
>>> > > We have in /proc/meminfo
>>> > >
>>> > > Hugepagesize: 2048 kB
>>> > >
>>> > > Does it makes it easy for application to find THP page size also there ?
>> >
>> > Nope. That's the default hugetlbfs page size. Even on x86, that can be
>> > changed and _could_ be 1G. If hugetlbfs is configured out, you also
>> > won't get this in meminfo.
> I think Aneesh propose to add one more line into the file.
Ahhh, ok...
Personally, I think Hugh did the right things. There's no reason to
waste cycles sticking a number in meminfo that never changes.
--
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:[~2016-12-06 19:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 6:05 [PATCH] mm: make transparent hugepage size public Hugh Dickins
2016-12-06 9:07 ` Aneesh Kumar K.V
2016-12-06 15:14 ` Dave Hansen
2016-12-06 17:19 ` Kirill A. Shutemov
2016-12-06 19:27 ` Dave Hansen [this message]
2016-12-07 4:13 ` Hugh Dickins
2016-12-06 21:37 ` Andrew Morton
2016-12-07 7:50 ` Michal Hocko
2016-12-07 8:04 ` Vlastimil Babka
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=db569a60-5dd1-b0a8-9fcb-6dd2106765ee@intel.com \
--to=dave.hansen@intel.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=gthelen@google.com \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--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).