03 December 2015 -- Yet another mailing list movelibrelist seems to be dead or at least broken.  I have recieved severalemails directly saying that patches were posted, but they never gotresponses and the archives always seem empty.  So we are moving the listagain.  This from here on out we will be usinglibhugetlbfs@googlegroups.comas our mailing list.  Please send patches to this list rather thancreating a pull request.03 June 2015  -- libhugetlbfs to find new homeAs part of the fall out from the recent hijacking various "unmaintained"projects, I no longer wish to host this (or any other) project atsourceforge.  Effective today, the new official home for libhugetlbfscode ishttps://github.com/libhugetlbfs/libhugetlbfsThe doubling of the name is unfortunate, but I wanted the repo to belongto the org of the same name so there it is.Please do not submit pull requests, they will be closed with a redirectto the mailing list (see below) at best, or ignored completely at worst.Tarballs of specific releases can still be downloaded using the githubDownload ZIP button from the appropriate tag (or branch).  The mailinglist will now hosted at librelists and can be found atlibhugetlbfs@librelist.comFor libhugetlbfs usage, see the HOWTO, for what has changed see NEWS,and for how to work with the project see SubmittingCode10/03/2006 -- libhugetlbfs-1.0 ReleasedAfter roughly one year in development, version 1.0 of libhugetlbfs is here.It can be downloaded from SourceForge or the OzLabs mirror:http://sourceforge.net/project/showfiles.php?group_id=156936http://libhugetlbfs.ozlabs.org/snapshots/After a series of preview releases, we have tested a huge array of thesupported usage scenarios using benchmarks and real HPC applications.Usability and reliability have greatly improved.  But... due to theincredible diversity of applications that exist, there is bound to be a fewthat will not work correctly.If using libhugetlbfs makes your application slower: * Play around with the different combinations of hugetlb malloc and the   two different supported link types to see which combination works best. * Keep in mind that huge pages are a niche performance tweak and are not   suitable for every type of application.  They are specifically known to   hurt performance in certain situations.If you experience problems: * You've already read the HOWTO document, but read through it again.  It   is full of hints, notes, warnings, and caveats that we have found over   time.  This is the best starting point for a quick resolution to your   issue. * Make sure you have enough huge pages allocated.  Even if you think you   have enough, try increasing it to a number you know you will not use. * Set HUGETLB_VERBOSE=99 and HUGETLB_DEBUG=yes.  These options increase   the verbosity of the library and enable extra checking to help diagnose   the problem.If the above steps do not help, send as much information about the problem(including all libhugetlbfs debug output) tolibhugetlbfs@googlegroups.com and we'll help out as much as wecan.  We will probably ask you to collect things like: straces,/proc/pid/maps and gdb back traces.