Description: Upstream changes introduced in version 2.11-0ubuntu1
 This patch has been created by dpkg-source during the package build.
 Here's the last changelog entry, hopefully it gives details on why
 those changes were made:
 .
 libhugetlbfs (2.11-0ubuntu1) natty; urgency=low
 .
   * libhugetlbfs 2.11 release.
   * Package linker scripts in the -dev package.
 .
 The person named in the Author field signed this changelog entry.
Author: Matthias Klose <doko@ubuntu.com>

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: <vendor|upstream|other>, <url of original patch>
Bug: <url in upstream bugtracker>
Bug-Debian: http://bugs.debian.org/<bugnumber>
Bug-Ubuntu: https://launchpad.net/bugs/<bugnumber>
Forwarded: <no|not-needed|url proving that it has been forwarded>
Reviewed-By: <name and email of someone who approved the patch>
Last-Update: <YYYY-MM-DD>

--- /dev/null
+++ libhugetlbfs-2.11/TODO.CONF
@@ -0,0 +1,64 @@
+Current configuration:
+ * Total System Memory......:  31580 MB
+ * Shared Mem Max Mapping...:     32 MB
+ * System Huge Page Size....:     16 MB
+ * Number of Huge Pages.....:      0
+ * Total size of Huge Pages.:      0 MB
+ * Remaining System Memory..:  31580 MB
+ * Huge Page User Group.....:  root (0)
+
+How much memory would you like to allocate for huge pages? (input in MB, unless postfixed with GB): 256
+Okay, we'll try to allocate 256 MB for huge pages...
+
+What group should have access to the huge pages?(The group will be created, if need be) [hugepages]: 
+Okay, we'll give group hugepages access to the huge pages
+Created group hugepages (gid 2502) for huge page use
+
+What user(s) should have access to the huge pages (space-delimited list, users created as needed)? 
+
+hugeadm:WARNING: There is no swap space configured, resizing hugepage pool may fail
+hugeadm:WARNING: Use --add-temp-swap option to temporarily add swap during the resize
+Saved original /etc/sysctl.conf as /etc/sysctl.conf.backup
+Saved original /etc/security/limits.d/hugepages.conf as /etc/security/limits.d/hugepages.conf.backup
+
+Final configuration:
+ * Total System Memory......:  31580 MB
+ * Shared Mem Max Mapping...:    256 MB
+ * System Huge Page Size....:     16 MB
+ * Available Huge Pages.....:     16
+ * Total size of Huge Pages.:    256 MB
+ * Remaining System Memory..:  31324 MB
+ * Huge Page User Group.....:  hugepages (2502)
+
+--- /etc/sysctl.conf.backup     2010-12-21 09:56:11.000000000 +0000
++++ /etc/sysctl.conf    2011-02-23 00:53:26.752252039 +0000
+@@ -58,3 +58,6 @@
+ # Log Martian Packets
+ #net.ipv4.conf.all.log_martians = 1
+ #
++kernel.shmmax = 268435456
++vm.nr_hugepages = 16
++vm.hugetlb_shm_group = 2502
+
+
+cat /etc/security/limits.d/hugepages.conf
+# limit.conf file for hugepages.
+#
+# The hugepages are always locked in memory, therefore it is
+# necessary to raise the memlock limit appropriately. Note that
+# memlock limit is not enforced to the hugetlbfs pseudo-filesystems.
+#
+# By default, pam_limits grant all users right to memlock a few pages
+# (see `ulimit -H -l'). When you raise the memlock limit for hugepages,
+# it is usually a good idea to grant those few extra KB too.
+# (for example: 256 * 1024K + 64K => 262144 )
+#
+# Documentations:
+#   * limits.conf(5), pam_limits(8) manpages
+#   * /usr/share/doc/hugepages/HOWTO.gz
+
+#<domain>        <type>  <item>          <value>
+
+#@hugepages      hard    memlock         262144
+#@hugepages      soft    memlock         262144
+
