From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Michal Hocko <mhocko@suse.cz>
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,
Wanpeng Li <liwanp@linux.vnet.ibm.com>
Subject: Re: [PATCH] mm/hugetlb: fix total hugetlbfs pages count when memory overcommit accouting
Date: Thu, 14 Mar 2013 18:15:58 +0800 [thread overview]
Message-ID: <20130314101558.GA19776@hacker.(null)> (raw)
In-Reply-To: <20130314094419.GA11631@dhcp22.suse.cz>
On Thu, Mar 14, 2013 at 10:44:19AM +0100, Michal Hocko wrote:
>On Wed 13-03-13 15:08:31, Wanpeng Li wrote:
>> After commit 42d7395f ("mm: support more pagesizes for MAP_HUGETLB/SHM_HUGETLB")
>> be merged, kernel permit multiple huge page sizes,
>
Hi Michal,
>multiple huge page sizes were possible long before this commit. The
>above mentioned patch just made their usage via IPC much easier. You
>could do the same previously (since a137e1cc) by mounting hugetlbfs with
>a specific page size as a parameter and using mmap.
>
Agreed.
>> and when the system administrator has configured the system to provide
>> huge page pools of different sizes, application can choose the page
>> size used for their allocation.
>
>> However, just default size of huge page pool is statistical when
>> memory overcommit accouting, the bad is that this will result in
>> innocent processes be killed by oom-killer later.
>
>Why would an innnocent process be killed? The overcommit calculation
>is incorrect, that is true, but this just means that an unexpected
>ENOMEM/EFAULT or SIGSEGV would be returned, no? How an OOM could be a
>result?
Agreed.
>
>> Fix it by statistic all huge page pools of different sizes provided by
>> administrator.
>
>The patch makes sense but the description is misleading AFAICS.
>
Thanks for your pointing out Michal, I will update the description. :-)
Regards,
Wanpeng Li
>> Testcase:
>> boot: hugepagesz=1G hugepages=1
>> before patch:
>> egrep 'CommitLimit' /proc/meminfo
>> CommitLimit: 55434168 kB
>> after patch:
>> egrep 'CommitLimit' /proc/meminfo
>> CommitLimit: 54909880 kB
>>
>> Signed-off-by: Wanpeng Li <liwanp@linux.vnet.ibm.com>
>> ---
>> mm/hugetlb.c | 7 +++++--
>> 1 file changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
>> index cdb64e4..9e25040 100644
>> --- a/mm/hugetlb.c
>> +++ b/mm/hugetlb.c
>> @@ -2124,8 +2124,11 @@ int hugetlb_report_node_meminfo(int nid, char *buf)
>> /* Return the number pages of memory we physically have, in PAGE_SIZE units. */
>> unsigned long hugetlb_total_pages(void)
>> {
>> - struct hstate *h = &default_hstate;
>> - return h->nr_huge_pages * pages_per_huge_page(h);
>> + struct hstate *h;
>> + unsigned long nr_total_pages = 0;
>> + for_each_hstate(h)
>> + nr_total_pages += h->nr_huge_pages * pages_per_huge_page(h);
>> + return nr_total_pages;
>> }
>>
>> static int hugetlb_acct_memory(struct hstate *h, long delta)
>> --
>> 1.7.11.7
>>
>> --
>> 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>
>
>--
>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 10:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 7:08 [PATCH] mm/hugetlb: fix total hugetlbfs pages count when memory overcommit accouting Wanpeng Li
2013-03-13 8:02 ` Hillf Danton
2013-03-13 8:32 ` Wanpeng Li
2013-03-13 8:32 ` Wanpeng Li
2013-03-13 16:59 ` Andi Kleen
2013-03-14 9:44 ` Michal Hocko
2013-03-14 10:15 ` Wanpeng Li [this message]
2013-03-14 10:15 ` 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='20130314101558.GA19776@hacker.(null)' \
--to=liwanp@linux.vnet.ibm.com \
--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=mhocko@suse.cz \
/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).