linux-kernel - Re: [PATCH] mm, vmscan: Give up balancing node for high order allocations earlier

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 11 Jul 2016 15:20:15 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Hillf Danton" <hillf.zj@...baba-inc.com>
Cc:	"'Mel Gorman'" <mgorman@...hsingularity.net>,
	"'Johannes Weiner'" <hannes@...xchg.org>,
	"'Vlastimil Babka'" <vbabka@...e.cz>,
	"'linux-kernel'" <linux-kernel@...r.kernel.org>,
	<linux-mm@...ck.org>
Subject: Re: [PATCH] mm, vmscan: Give up balancing node for high order
 allocations earlier

On Wed, 29 Jun 2016 13:42:12 +0800 "Hillf Danton" <hillf.zj@...baba-inc.com> wrote:

> To avoid excessive reclaim, we give up rebalancing for high order 
> allocations right after reclaiming enough pages.

hm.  What are the observed runtime effects of this change?  Any testing
results?