Thanks for the info. Unfortunately, I already have the code to open and
mmap a file in the hugetlbfs. What I am looking for is an allocator that
will go on top of this with an explicit interface, like
huge_malloc(bytes).
My concern with sending *all* my mallocs to huge pages is that my app has
many mallocs will have no benefit from being satisfied from large pages,
and these could wind up fragmenting the large page storage area to the
point that the structures that really do need to be in large pages won't
fit there.
Mike
[EMAIL PROTECTED] wrote on 10/03/2007 08:54:50 AM:
> Hi Mike. I've cc'ed our development list on this reply...
>
> You have a number of options for using the library depending on your
> needs.
>
> If you would like to transparently back all of your application's malloc
> calls with huge pages, you can use the library as an LD_PRELOAD and
> specify HUGETLB_MORECORE=yes in the environment.
>
> If you prefer to manually allocate huge pages, we provide
> hugetlbfs_unlinked_fd(). This function locates a mounted hugetlbfs
> filesystem and returns an open and unlinked file descriptor created on
> that fs. This fd is ready for calls to mmap(). See the tests/
> directory for programming examples.
>
> Hope this helps :)
>
> --
> Adam Litke - (agl at us.ibm.com)
> IBM Linux Technology Center
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Libhugetlbfs-devel mailing list
Libhugetlbfs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libhugetlbfs-devel
