From: Michal Hocko <mhocko@suse.cz>
To: Wanpeng Li <liwanp@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Hillf Danton <dhillf@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm/hugetlb: fix total hugetlbfs pages count when memory overcommit accouting
Date: Thu, 14 Mar 2013 13:58:27 +0100 [thread overview]
Message-ID: <20130314125827.GD11631@dhcp22.suse.cz> (raw)
In-Reply-To: <20130314112411.GA26630@hacker.(null)>
On Thu 14-03-13 19:24:11, Wanpeng Li wrote:
> On Thu, Mar 14, 2013 at 12:09:27PM +0100, Michal Hocko wrote:
> >On Thu 14-03-13 18:49:49, Wanpeng Li wrote:
> >> Changelog:
> >> v1 -> v2:
> >> * update patch description, spotted by Michal
> >>
> >> hugetlb_total_pages() does not account for all the supported hugepage
> >> sizes.
> >
> >> This can lead to incorrect calculation of the total number of
> >> page frames used by hugetlb. This patch corrects the issue.
> >
>
> Hi Michal,
>
> >Sorry to be so picky but this doesn't tell us much. Why do we need to
> >have the total number of hugetlb pages?
> >
> >What about the following:
> >"hugetlb_total_pages is used for overcommit calculations but the
> >current implementation considers only default hugetlb page size (which
> >is either the first defined hugepage size or the one specified by
> >default_hugepagesz kernel boot parameter).
> >
> >If the system is configured for more than one hugepage size (which is
> >possible since a137e1cc hugetlbfs: per mount huge page sizes) then
> >the overcommit estimation done by __vm_enough_memory (resp. shown by
> >meminfo_proc_show) is not precise - there is an impression of more
> >available/allowed memory. This can lead to an unexpected ENOMEM/EFAULT
> >resp. SIGSEGV when memory is accounted."
> >
>
> Fair enough, thanks. :-)
>
> >I think this is also worth pushing to the stable tree (it goes back to
> >2.6.27)
> >
>
> Yup, I will Cc Greg in next version.
Ccing Greg doesn't help. All that is required is:
Cc: stable@vger.kernel.org # 2.6.27+
> >> Testcase:
> >> boot: hugepagesz=1G hugepages=1
> >> before patch:
> >> egrep 'CommitLimit' /proc/meminfo
> >> CommitLimit: 55434168 kB
> >> after patch:
> >> egrep 'CommitLimit' /proc/meminfo
> >> CommitLimit: 54909880 kB
> >
> >This gives some more confusion to a reader because there is only
> >something like 500M difference here without any explanation.
> >
>
> the default overcommit ratio is 50.
And that part was missing in the description...
[...]
--
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:[~2013-03-14 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 10:49 Wanpeng Li
2013-03-14 11:09 ` Michal Hocko
2013-03-14 11:24 ` Wanpeng Li
2013-03-14 12:58 ` Michal Hocko [this message]
2013-03-14 11:24 ` Wanpeng Li
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=20130314125827.GD11631@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dhillf@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.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