Re: too big min_free_kbytes
From: Mel Gorman <hidden>
Date: 2011-02-24 09:52:39
On Thu, Feb 24, 2011 at 04:08:47PM +0800, Shaohua Li wrote:
On Wed, 2011-02-23 at 22:45 +0800, Andrea Arcangeli wrote:quoted
On Wed, Feb 23, 2011 at 01:29:14PM +0800, Shaohua Li wrote:quoted
Fixing it will let more people enable THP by default. but anyway we will disable it now if the issue can't be fixed.Did you try what happens with transparent_hugepage=madvise? If that doesn't fix it, it's min_free_kbytes issue.with madvise, the min_free_kbytes is still high (same as the 'always' case).
This high min_free_kbytes is expected and is not considered a bug as it's related to transparent hugepages being able to allocate huge pages for a long period of time. Essentially, it's a cost of using hugepages.
The result is still we have about 50M memory is reserved. you can try at your machine with boot option 'mem=2G' and check the zoneinfo output.
Is the actual free memory around the 50M mark or is it far higher than it should be? -- Mel Gorman SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>