[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1110181806570.12850@chino.kir.corp.google.com>
Date: Tue, 18 Oct 2011 18:16:21 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Andi Kleen <andi@...stfloor.org>
cc: Dimitri Sivanich <sivanich@....com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Christoph Lameter <cl@...two.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Mel Gorman <mel@....ul.ie>
Subject: Re: [PATCH] Reduce vm_stat cacheline contention in
__vm_enough_memory
On Tue, 18 Oct 2011, Andi Kleen wrote:
> > Would it make sense to have the ZVC delta be tuneable (via /proc/sys/vm?), keeping the
> > same default behavior as what we currently have?
>
> Tunable is bad. We don't really want a "hundreds of lines magic shell script to
> make large systems perform". Please find a way to auto tune.
>
Agreed, and I think even if we had a tunable that it would result in
potentially erradic VM performance because some areas depend on "fairly
accurate" ZVCs and it wouldn't be clear that you're trading other unknown
VM issues that will affect your workload because you've increased the
deltas. Let's try to avoid having to ask "what is your ZVC delta tunable
set at?" when someone reports a bug about reclaim stopping preemptively.
That said, perhaps we need higher deltas by default and then hints in key
areas in the form of sync_stats_if_delta_above(x) calls that would do
zone_page_state_add() only when that kind of precision is actually needed.
For public interfaces, that would be very easy to audit to see what the
level of precision is when parsing the data.
--
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/
Powered by blists - more mailing lists