On 12/31/2013 04:29 PM, Han Pingtian wrote:
> min_free_kbytes may be updated during thp's initialization. Sometimes,
> this will change the value being set by user. Showing message will
> clarify this confusion.
...
> - if (recommended_min > min_free_kbytes)
> + if (recommended_min > min_free_kbytes) {
> min_free_kbytes = recommended_min;
> + pr_info("min_free_kbytes is updated to %d by enabling transparent hugepage.\n",
> + min_free_kbytes);
> + }
"updated" doesn't tell us much. It's also kinda nasty that if we enable
then disable THP, we end up with an elevated min_free_kbytes. Maybe we
should at least put something in that tells the user how to get back
where they were if they care:
"raising min_free_kbytes from %d to %d to help transparent hugepage
allocations"
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>