From: Mel Gorman <mel@csn.ul.ie>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, kniht@linux.vnet.ibm.com,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [PATCH 1/2] powerpc: add hugepagesz boot-time parameter
Date: Wed, 28 Nov 2007 16:12:02 +0000 [thread overview]
Message-ID: <20071128161201.GA10916@csn.ul.ie> (raw)
In-Reply-To: <200711280826.46820.arnd@arndb.de>
On (28/11/07 08:26), Arnd Bergmann didst pronounce:
> On Wednesday 28 November 2007, Jon Tollefson wrote:
> > This patch adds the hugepagesz boot-time parameter for ppc64 that lets
> > you pick the size for your huge pages. The choices available are 64K
> > and 16M. It defaults to 16M (previously the only choice) if nothing or
> > an invalid choice is specified. Tested 64K huge pages with the
> > libhugetlbfs 1.2 release with its 'make func' and 'make stress' test
> > invocations.
>
> How hard would it be to add the 1MB page size that some CPUs support
> as well? On systems with small physical memory like the PS3, that
> sounds very useful to me.
>
Does the PS3 support 1M pages in hardware? When I last looked, the magic
ibm,segment-page-sizes file that described the supported pagesizes was
missing from the device tree. In this situation, the default sizes
become 4K and 16M because no other ones are advertised.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
next prev parent reply other threads:[~2007-11-28 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 5:03 [PATCH 1/2] powerpc: add hugepagesz boot-time parameter Jon Tollefson
2007-11-28 7:26 ` Arnd Bergmann
2007-11-28 16:12 ` Mel Gorman [this message]
2007-11-28 16:30 ` Arnd Bergmann
2007-11-28 21:22 ` Geoff Levand
2007-11-28 21:28 ` Randy Dunlap
2007-11-29 1:36 ` Nish Aravamudan
2007-11-29 1:40 ` Randy Dunlap
2007-11-29 3:01 ` Nish Aravamudan
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=20071128161201.GA10916@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=arnd@arndb.de \
--cc=kniht@linux.vnet.ibm.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
/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).