On Tue, Oct 21, 2008 at 09:06:29AM +0100, Eric B Munson wrote:
> This patch Adjusts the HOWTO section on sizing huge page pools to reference
> the hugeadm utlity.
> 
> Also it changes the number of pages from 20 to 25 for most test cases and
> calls out PowerPC 64kb pages as a specific instance where more than 25 pages
> will be necessary for test suite completion.
> 
> Signed-off-by: Eric B Munson <[EMAIL PROTECTED]>
> ---
>  HOWTO |   20 ++++++++++++++++----
>  1 files changed, 16 insertions(+), 4 deletions(-)
> 
> diff --git a/HOWTO b/HOWTO
> index 260d8cf..c4094a0 100644
> --- a/HOWTO
> +++ b/HOWTO
> @@ -102,6 +102,13 @@ recommended.  Older versions will work with restricted 
> functionality.
>  
>  Configuration prerequisites
>  ---------------------------
> +Direct access to hugepage pool size control has been deprecated in for

"deprecated -in- for"
"deprecated in [something or other] for"

either we don't need the in, or we we need an in to in

> +the hugeadm utility.  The utility provides a simple method for controlling

".  -The-[This] "

> +finding available huge page pools and adjusting static pool size or dynamic

"controlling [and] finding" perhaps?

> +pool size depending on kernel support.

perhaps "... static and dynamic pool size where available."

> +
> +The following methods for adjusting huge page pools will still be available
> +in addition to the hugeadm utility.
>  
>  In kernels before 2.6.24, hugepages must be allocated at boot-time via
>  the hugepages= command-line parameter or at run-time via the
> @@ -115,11 +122,15 @@ should be set to the maximum size of the hugepage pool. 
> No hugepages
>  need to be allocated via /proc/sys/vm/nr_hugepages or hugepages= in this
>  case. Hugepages so allocated will be in the dynamic hugepage pool.
>  
> -For the running of the libhugetlbfs testsuite (see below), allocating 20
> +For the running of the libhugetlbfs testsuite (see below), allocating 25
>  static hugepages is recommended. Due to memory restrictions, the number
>  of hugepages requested may not be allocated if the allocation is
>  attempted at run-time. Users should verify the actual number of
> -hugepages allocated by either
> +hugepages allocated using one of the following:
> +
> +       hugeadm --pool-list
> +

You give a direct example for pool listing, but there was no example for
how to change the pool.  I wonder if there should be.

> +or
>  
>         cat /proc/sys/vm/nr_hugepages

What about the sysfs files for the other sizes, perhaps those should be
exposed?

>  
> @@ -127,8 +138,9 @@ or
>  
>         grep HugePages_Free /proc/meminfo
>  
> -With 20 hugepages allocated, most tests should succeed. However, with
> -smaller hugepages sizes, many more hugepages may be necessary.
> +With 25 hugepages allocated, most tests should succeed. However, with
> +smaller hugepages sizes, (like PowerPC 64kb pages) many more hugepages
> +may be necessary.
>  
>  To use libhugetlbfs features, as well as to run the testsuite, hugetlbfs
>  must be mounted:
> -- 
> 1.5.6.1

Ok this sounds sensbible.  I am supprised there are so few updates
though.  We must not mention the pool much at all.

-apw

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Libhugetlbfs-devel mailing list
Libhugetlbfs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libhugetlbfs-devel

Reply via email to