From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933132AbcDLTzM (ORCPT ); Tue, 12 Apr 2016 15:55:12 -0400 Received: from prod-mail-xrelay07.akamai.com ([23.79.238.175]:19129 "EHLO prod-mail-xrelay07.akamai.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754397AbcDLTzK (ORCPT ); Tue, 12 Apr 2016 15:55:10 -0400 From: Jason Baron To: akpm@linux-foundation.org, kirill.shutemov@linux.intel.com Cc: rientjes@google.com, aarcange@redhat.com, mgorman@techsingularity.net, mhocko@suse.com, hannes@cmpxchg.org, vbabka@suse.cz, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: [PATCH 0/1] mm: setting of min_free_kbytes Date: Tue, 12 Apr 2016 15:54:36 -0400 Message-Id: X-Mailer: git-send-email 1.9.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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