[PATCH 0/1] mm: setting of min_free_kbytes

[Jason Baron <jbaron@akamai.com>]

Hi,

While updating a workload to a 4.1 kernel (from 3.14), I found that
min_free_kbytes was automatically set to 11365, whereas on 3.14 it was
67584. This is caused by a change to how min_free_kbytes is set when
CONFIG_TRANSPARENT_HUGEPAGE=y, which is detailed in the patch that
follows.

I was wondering as well if the setting of min_free_kbytes could be
improved in the following cases while looking at this code:

1) memory hotplug

we call init_per_zone_wmark_min() but not
set_recommended_min_free_kbytes() (for hugepages)

2) when khugepaged is stopped

Do we want to undo any settings thath khugepaged has done in that
case to restore the default settings

Thanks,

-Jason

Jason Baron (1):
  mm: update min_free_kbytes from khugepaged after core initialization

 mm/page_alloc.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.6.1

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>