linux-kernel - Re: [RFC PATCH 0/7] Configurable fair allocation zone policy v2r6

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: <52B068B7.4070304@bitsync.net>
Date:	Tue, 17 Dec 2013 16:07:35 +0100
From:	Zlatko Calusic <zcalusic@...sync.net>
To:	Mel Gorman <mgorman@...e.de>
CC:	Johannes Weiner <hannes@...xchg.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Dave Hansen <dave.hansen@...el.com>,
	Rik van Riel <riel@...hat.com>,
	Linux-MM <linux-mm@...ck.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 0/7] Configurable fair allocation zone policy v2r6

On 13.12.2013 15:10, Mel Gorman wrote:
> Kicked this another bit today. It's still a bit half-baked but it restores
> the historical performance and leaves the door open at the end for playing
> nice with distributing file pages between nodes. Finishing this series
> depends on whether we are going to make the remote node behaviour of the
> fair zone allocation policy configurable or redefine MPOL_LOCAL. I'm in
> favour of the configurable option because the default can be redefined and
> tested while giving users a "compat" mode if we discover the new default
> behaviour sucks for some workload.
>

I'll start a 5-day test of this patchset in a few hours, unless you can 
send an updated one in the meantime. I intend to test it on a rather 
boring 4GB x86_64 machine that before Johannes' work had lots of trouble 
balancing zones. Would you recommend to use the default settings, i.e. 
don't mess with tunables at this point?

Regards,
-- 
Zlatko

--
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/