linux-kernel - [PATCH 0/1] mm: setting of min_free

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <cover.1460488349.git.jbaron@akamai.com>
Date:	Tue, 12 Apr 2016 15:54:36 -0400
From:	Jason Baron <jbaron@...mai.com>
To:	akpm@...ux-foundation.org, kirill.shutemov@...ux.intel.com
Cc:	rientjes@...gle.com, aarcange@...hat.com,
	mgorman@...hsingularity.net, mhocko@...e.com, hannes@...xchg.org,
	vbabka@...e.cz, linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/1] mm: setting of min_free_kbytes

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