linux-kernel - Re: [PATCH 1/3] mm: vmscan: Remove lumpy reclaim

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]

Message-ID: <CAHGf_=rm0m4XZn=BJ8uLnarq9MwSvFbQMW=5ueRzM8ezincKmA@mail.gmail.com>
Date:	Wed, 11 Apr 2012 14:54:04 -0400
From:	KOSAKI Motohiro <kosaki.motohiro@...il.com>
To:	Rik van Riel <riel@...hat.com>
Cc:	Mel Gorman <mgorman@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Konstantin Khlebnikov <khlebnikov@...nvz.org>,
	Hugh Dickins <hughd@...gle.com>, Ying Han <yinghan@...gle.com>,
	Linux-MM <linux-mm@...ck.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] mm: vmscan: Remove lumpy reclaim

On Wed, Apr 11, 2012 at 1:25 PM, Rik van Riel <riel@...hat.com> wrote:
> On 04/11/2012 12:38 PM, Mel Gorman wrote:
>>
>> Lumpy reclaim had a purpose but in the mind of some, it was to kick
>> the system so hard it trashed. For others the purpose was to complicate
>> vmscan.c. Over time it was giving softer shoes and a nicer attitude but
>> memory compaction needs to step up and replace it so this patch sends
>> lumpy reclaim to the farm.
>>
>> The tracepoint format changes for isolating LRU pages with this patch
>> applied. Furthermore reclaim/compaction can no longer queue dirty pages in
>> pageout() if the underlying BDI is congested. Lumpy reclaim used this
>> logic
>> and reclaim/compaction was using it in error.
>>
>> Signed-off-by: Mel Gorman<mgorman@...e.de>
>
> Acked-by: Rik van Riel <riel@...hat.com>

Acked-by: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/