From: Andi Kleen <andi@firstfloor.org>
To: Ric Mason <ric.masonn@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-mm@kvack.org, Hillf Danton <dhillf@gmail.com>
Subject: Re: Support variable-sized huge pages
Date: Tue, 5 Feb 2013 15:08:52 +0100 [thread overview]
Message-ID: <20130205140852.GU30577@one.firstfloor.org> (raw)
In-Reply-To: <1360043326.2403.2.camel@kernel.cn.ibm.com>
On Mon, Feb 04, 2013 at 11:48:46PM -0600, Ric Mason wrote:
> Hi Andi,
> On Thu, 2013-01-31 at 11:52 +0100, Andi Kleen wrote:
> > On Thu, Jan 31, 2013 at 02:23:10AM -0600, Ric Mason wrote:
> > > Hi all,
> > >
> > > It seems that Andi's "Support more pagesizes for
> > > MAP_HUGETLB/SHM_HUGETLB" patch has already merged. According to the
> > > patch, x86 will support 2MB and 1GB huge pages. But I just see
> > > hugepages-2048kB under /sys/kernel/mm/hugepages/ on my x86_32 PAE desktop.
> > > Where is 1GB huge pages?
> >
> > 1GB pages are only supported under 64bit kernels, and also
> > only if you allocate them explicitely with boot options.
>
> I am curious about how can buddy system alloc 1GB huge pages? the most
> order buddy system supports is 10. Could you explain to me?
It can't, that is why you can only allocate them at boot time.
-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>
next prev parent reply other threads:[~2013-02-05 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 8:23 Ric Mason
2013-01-31 8:57 ` Jianguo Wu
2013-01-31 10:52 ` Andi Kleen
2013-02-05 5:48 ` Ric Mason
2013-02-05 9:51 ` Michal Hocko
2013-02-05 14:08 ` Andi Kleen [this message]
2013-02-24 7:00 ` Ric Mason
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=20130205140852.GU30577@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=dhillf@gmail.com \
--cc=linux-mm@kvack.org \
--cc=ric.masonn@gmail.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