From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Cc: mel@csn.ul.ie, Jon Tollefson <kniht@linux.vnet.ibm.com>,
csnook@redhat.com, Paul Mackerras <paulus@samba.org>,
David Gibson <dwg@au1.ibm.com>
Subject: Re: [PATCh v3] powerpc: add hugepagesz boot-time parameter
Date: Fri, 4 Jan 2008 00:34:24 +0100 [thread overview]
Message-ID: <200801040034.25329.arnd@arndb.de> (raw)
In-Reply-To: <477D68E6.2070108@linux.vnet.ibm.com>
On Thursday 03 January 2008, Jon Tollefson wrote:
> Paul, please include this in 2.6.25 if there are no objections.
No objections to this version from me, just questions.
> This patch adds the hugepagesz boot-time parameter for ppc64. =A0It lets
> one pick the size for huge pages. The choices available are 64K and 16M
> when the base page size is 4k. It defaults to 16M (previously the only
> only choice) if nothing or an invalid choice is specified.
We started discussing this in v1, but the discussion got sidetracked:
Is there a technical reason why you don't also allow 1M pages, which
may be useful in certain scenarios?
On the Cell/B.E. platforms (IBM/Mercury blades, Toshiba Celleb, PS3), the
second large page size is an option that can be set in a HID SPR
to either 64KB or 1MB. Unfortunately, we can't do these two simultaneously,
but the firmware can change the default and put it into the device tree,
or you could have the kernel override the firmware settings.
Going a lot further, do you have plans for a fully dynamic hugepage size,
e.g. using a mount option for hugetlbfs? I can see that as rather useful,
but at the same time it's probably much more complicated than the boot time
option.
Arnd <><
next prev parent reply other threads:[~2008-01-03 23:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 22:59 [PATCh v3] powerpc: add hugepagesz boot-time parameter Jon Tollefson
2008-01-03 23:34 ` Arnd Bergmann [this message]
2008-01-04 20:00 ` Jon Tollefson
2008-01-04 23:03 ` Arnd Bergmann
2008-01-07 12:04 ` Mel Gorman
2008-01-07 12:37 ` Arnd Bergmann
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=200801040034.25329.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=csnook@redhat.com \
--cc=dwg@au1.ibm.com \
--cc=kniht@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mel@csn.ul.ie \
--cc=paulus@samba.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).