Adam Litke wrote: > The obvious answer is to let the hugetlb pool grow and shrink in response to > the runtime demand for huge pages. The work Mel Gorman has been doing to > establish a memory zone for movable memory allocations makes dynamically > resizing the hugetlb pool reliable within the limits of that zone. This patch > series implements dynamic pool resizing for private and shared mappings while > being careful to maintain existing semantics. Please reply with your comments > and feedback; even just to say whether it would be a useful feature to you.
Thanks, this will be extremely useful for our customers' workloads. -Andrew Hastings Cray Inc. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Libhugetlbfs-devel mailing list Libhugetlbfs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libhugetlbfs-devel
