From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: David Rientjes <rientjes@google.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
Mel Gorman <mel@csn.ul.ie>, Nishanth Aravamudan <nacc@us.ibm.com>,
Adam Litke <agl@us.ibm.com>, Andy Whitcroft <apw@canonical.com>,
eric.whitney@hp.com
Subject: Re: [PATCH 5/5] Update huge pages kernel documentation
Date: Thu, 18 Jun 2009 15:06:58 -0400 [thread overview]
Message-ID: <1245352018.1025.86.camel@lts-notebook> (raw)
In-Reply-To: <9ec263480906181149t1aac592o57ce517bdd749cf5@mail.gmail.com>
On Thu, 2009-06-18 at 11:49 -0700, David Rientjes wrote:
> On Tue, Jun 16, 2009 at 6:53 AM, Lee
> Schermerhorn<lee.schermerhorn@hp.com> wrote:
> > @@ -67,26 +65,76 @@ use either the mmap system call or share
> > the huge pages. It is required that the system administrator preallocate
> > enough memory for huge page purposes.
> >
> > -Use the following command to dynamically allocate/deallocate hugepages:
> > +The administrator can preallocate huge pages on the kernel boot command line by
> > +specifying the "hugepages=N" parameter, where 'N' = the number of huge pages
> > +requested. This is the most reliable method for preallocating huge pages as
> > +memory has not yet become fragmented.
> > +
> > +Some platforms support multiple huge page sizes. To preallocate huge pages
> > +of a specific size, one must preceed the huge pages boot command parameters
> > +with a huge page size selection parameter "hugepagesz=<size>". <size> must
> > +be specified in bytes with optional scale suffix [kKmMgG]. The default huge
> > +page size may be selected with the "default_hugepagesz=<size>" boot parameter.
> > +
> > +/proc/sys/vm/nr_hugepages indicates the current number of configured [default
> > +size] hugetlb pages in the kernel. Super user can dynamically request more
> > +(or free some pre-configured) hugepages.
> > +
> > +Use the following command to dynamically allocate/deallocate default sized
> > +hugepages:
> >
> > echo 20 > /proc/sys/vm/nr_hugepages
> >
> > -This command will try to configure 20 hugepages in the system. The success
> > -or failure of allocation depends on the amount of physically contiguous
> > -memory that is preset in system at this time. System administrators may want
> > -to put this command in one of the local rc init files. This will enable the
> > -kernel to request huge pages early in the boot process (when the possibility
> > -of getting physical contiguous pages is still very high). In either
> > -case, administrators will want to verify the number of hugepages actually
> > -allocated by checking the sysctl or meminfo.
> > +This command will try to configure 20 default sized hugepages in the system.
> > +On a NUMA platform, the kernel will attempt to distribute the hugepage pool
> > +over the nodes specified by the /proc/sys/vm/hugepages_nodes_allowed node mask.
> > +hugepages_nodes_allowed defaults to all on-line nodes.
> > +
> > +To control the nodes on which huge pages are preallocated, the administrator
> > +may set the hugepages_nodes_allowed for the default huge page size using:
> > +
> > + echo <nodelist> >/proc/sys/vm/hugepages_nodes_allowed
> > +
>
> This probably also needs an update to
> Documentation/ABI/testing/sysfs-kernel-mm-hugepages for the
> non-default hstate nodes_allowed.
Thanks, David. I'll take a look and address that in the next respin of
the series. If you've been following the exchange with Mel, you'll know
that the approach may change quite a bit. However it ends up, I'll
update the abi testing doc or yell for help.
Lee
--
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:[~2009-06-18 19:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 13:52 [PATCH 0/5] Huge Pages Nodes Allowed Lee Schermerhorn
2009-06-16 13:52 ` [PATCH 1/5] Free huge pages round robin to balance across nodes Lee Schermerhorn
2009-06-17 13:18 ` Mel Gorman
2009-06-17 17:16 ` Lee Schermerhorn
2009-06-18 19:08 ` David Rientjes
2009-06-16 13:52 ` [PATCH 2/5] Add nodes_allowed members to hugepages hstate struct Lee Schermerhorn
2009-06-17 13:35 ` Mel Gorman
2009-06-17 17:38 ` Lee Schermerhorn
2009-06-18 9:17 ` Mel Gorman
2009-06-16 13:53 ` [PATCH 3/5] Use per hstate nodes_allowed to constrain huge page allocation Lee Schermerhorn
2009-06-17 13:39 ` Mel Gorman
2009-06-17 17:47 ` Lee Schermerhorn
2009-06-18 9:18 ` Mel Gorman
2009-06-16 13:53 ` [PATCH 4/5] Add sysctl for default hstate nodes_allowed Lee Schermerhorn
2009-06-17 13:41 ` Mel Gorman
2009-06-17 17:52 ` Lee Schermerhorn
2009-06-18 9:19 ` Mel Gorman
2009-06-16 13:53 ` [PATCH 5/5] Update huge pages kernel documentation Lee Schermerhorn
2009-06-18 18:49 ` David Rientjes
2009-06-18 19:06 ` Lee Schermerhorn [this message]
2009-06-17 13:02 ` [PATCH 0/5] Huge Pages Nodes Allowed Mel Gorman
2009-06-17 17:15 ` Lee Schermerhorn
2009-06-18 9:33 ` Mel Gorman
2009-06-18 14:46 ` Lee Schermerhorn
2009-06-18 15:00 ` Mel Gorman
2009-06-18 19:08 ` David Rientjes
2009-06-24 7:11 ` David Rientjes
2009-06-24 11:25 ` Lee Schermerhorn
2009-06-24 22:26 ` David Rientjes
2009-06-25 2:14 ` Lee Schermerhorn
2009-06-25 19:22 ` David Rientjes
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=1245352018.1025.86.camel@lts-notebook \
--to=lee.schermerhorn@hp.com \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=eric.whitney@hp.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=nacc@us.ibm.com \
--cc=rientjes@google.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).