From: Andi Kleen <ak@linux.intel.com>
To: Wanpeng Li <wanpeng.li@linux.intel.com>
Cc: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>,
Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Michal Hocko <mhocko@suse.cz>, Mel Gorman <mgorman@suse.de>,
Rik van Riel <riel@redhat.com>, Hillf Danton <dhillf@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] mm/hugetlb: gigantic hugetlb page pools shrink supporting
Date: Fri, 22 Aug 2014 07:18:07 -0700 [thread overview]
Message-ID: <20140822141807.GA5803@tassilo.jf.intel.com> (raw)
In-Reply-To: <20140822040420.GA4756@kernel>
> >commit 944d9fec8d7aee3f2e16573e9b6a16634b33f403
> >Author: Luiz Capitulino <lcapitulino@redhat.com>
> >Date: Wed Jun 4 16:07:13 2014 -0700
> >
> > hugetlb: add support for gigantic page allocation at runtime
> >
> >
>
> Ah, thanks for your pointing out.
I should add the CMA allocation would still make sense, as CMA would do
compaction and better pre-allocation while this does not. Should probably
revisit the issue. But it's at least partially solved now.
-Andi
--
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>
prev parent reply other threads:[~2014-08-22 14:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 9:09 [PATCH 0/6] mm/hugetlb: gigantic hugetlb page pools shrink supporting Wanpeng Li
2013-04-04 9:09 ` [PATCH 1/6] mm/hugetlb: introduce new sysctl knob which control gigantic page pools shrinking Wanpeng Li
2013-04-04 9:09 ` [PATCH 2/6] mm/hugetlb: update_and_free_page gigantic pages awareness Wanpeng Li
2013-04-04 9:09 ` [PATCH 3/6] mm/hugetlb: enable gigantic hugetlb page pools shrinking Wanpeng Li
2013-04-04 9:09 ` [PATCH 4/6] mm/hugetlb: use already exist huge_page_order() instead of h->order Wanpeng Li
2013-04-04 9:09 ` [PATCH 5/6] mm/hugetlb: remove redundant hugetlb_prefault Wanpeng Li
2013-04-04 9:09 ` [PATCH 6/6] mm/hugetlb: use already exist interface huge_page_shift Wanpeng Li
2013-04-04 16:17 ` [PATCH 0/6] mm/hugetlb: gigantic hugetlb page pools shrink supporting Michal Hocko
2013-04-04 16:20 ` Michal Hocko
2013-04-05 1:29 ` Wanpeng Li
2013-04-05 1:29 ` Wanpeng Li
2013-04-04 23:41 ` Wanpeng Li
2013-04-04 23:41 ` Wanpeng Li
2013-04-05 8:12 ` Michal Hocko
2013-04-05 8:27 ` Wanpeng Li
2013-04-05 9:27 ` Michal Hocko
2013-04-05 8:27 ` Wanpeng Li
2013-04-05 8:54 ` Simon Jeons
2013-04-05 9:52 ` Michal Hocko
2013-04-04 23:35 ` Wanpeng Li
2013-04-04 23:35 ` Wanpeng Li
2013-04-11 23:29 ` Wanpeng Li
2013-04-11 23:29 ` Wanpeng Li
2013-04-12 15:22 ` Andi Kleen
2013-07-15 11:31 ` Wanpeng Li
2013-07-15 11:31 ` Wanpeng Li
2014-08-21 23:37 ` Wanpeng Li
2014-08-22 1:34 ` Zhang Yanfei
2014-08-22 4:04 ` Wanpeng Li
2014-08-22 14:18 ` Andi Kleen [this message]
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=20140822141807.GA5803@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.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=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=riel@redhat.com \
--cc=wanpeng.li@linux.intel.com \
--cc=zhangyanfei@cn.fujitsu.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).