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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Thu, 22 May 2014 12:04:12 -0400
From:	Rik van Riel <>
To:	Mel Gorman <>,
	Andrew Morton <>
CC:	Johannes Weiner <>,
	Hugh Dickins <>,
	Tim Chen <>,
	Dave Chinner <>,
	Yuanhan Liu <>,
	Bob Liu <>, Jan Kara <>,
	Linux Kernel <>,
	Linux-MM <>,
	Linux-FSDevel <>
Subject: Re: [PATCH 3/3] mm: vmscan: Use proportional scanning during direct
 reclaim and full scan at DEF_PRIORITY

On 05/22/2014 05:09 AM, Mel Gorman wrote:
> Commit "mm: vmscan: obey proportional scanning requirements for kswapd"
> ensured that file/anon lists were scanned proportionally for reclaim from
> kswapd but ignored it for direct reclaim. The intent was to minimse direct
> reclaim latency but Yuanhan Liu pointer out that it substitutes one long
> stall for many small stalls and distorts aging for normal workloads like
> streaming readers/writers.  Hugh Dickins pointed out that a side-effect of
> the same commit was that when one LRU list dropped to zero that the entirety
> of the other list was shrunk leading to excessive reclaim in memcgs.
> This patch scans the file/anon lists proportionally for direct reclaim
> to similarly age page whether reclaimed by kswapd or direct reclaim but
> takes care to abort reclaim if one LRU drops to zero after reclaiming the
> requested number of pages.

> Note that there are fewer allocation stalls even though the amount
> of direct reclaim scanning is very approximately the same.
> Signed-off-by: Mel Gorman <>

Acked-by: Rik van Riel <>

All rights reversed
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists