hugepage: use the example from hugepages.cfg

Change-Id: I2ae7e111768fa0d29e5e1c7ff21dba181522d8f0
Signed-off-by: Sona Sarmadi <sona.sarmadi@enea.com>

1 files changed, 9 insertions, 8 deletions

diff --git a/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml b/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml
index f9558b2..9e574f6 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml
@@ -603,28 +603,29 @@ run</programlisting>
 
       <programlisting> hugepage_setup = auto
  threshold_to_use_1g = 8192
- percent_os_alloc = 50
- maximum_os_alloc_mb = 1024</programlisting>
+ percent_os_alloc = 30
+ maximum_os_alloc_mb = 2048</programlisting>
 
       <para>The following possible allocations could result (based on total
       system memory available):</para>
 
       <itemizedlist>
         <listitem>
-          <para>2GB of memory: 1024MB allocated for OS and 1024MB allocated as
-          2MB hugepages.</para>
+          <para>2GB of memory: approximately 30% will be allocated for the OS
+           and the rest will be allocated as 2MB hugepages.</para>
         </listitem>
 
         <listitem>
-          <para>4GB of memory: 1024MB allocated for OS and 3072MB allocated as
-          2MB hugepages.</para>
+          <para>4GB of memory: approximately 30% will be allocated for the OS
+          and the rest will be allocated as 2MB hugepages.</para>
         </listitem>
 
         <listitem>
-          <para>16GB of memory: 2GB allocated for OS and 14GB as 1GB
-          hugepages.</para>
+          <para>16GB of memory: 2GB allocated for OS and  the rest as 1GB Hugepages.</para>
         </listitem>
       </itemizedlist>
+      <note><para>The memory allocated for the kernel and hugepages might
+       vary slightly depending on how much memory is available.</para></note>
     </section>
 
     <section id="hugepage_customizing_man">