[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170718044521.GO3441@tassilo.jf.intel.com>
Date: Mon, 17 Jul 2017 21:45:21 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: "Li, Aubrey" <aubrey.li@...ux.intel.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Christoph Lameter <cl@...ux.com>,
Aubrey Li <aubrey.li@...el.com>, tglx@...utronix.de,
len.brown@...el.com, rjw@...ysocki.net, tim.c.chen@...ux.intel.com,
arjan@...ux.intel.com, paulmck@...ux.vnet.ibm.com,
yang.zhang.wz@...il.com, x86@...nel.org,
linux-kernel@...r.kernel.org, daniel.lezcano@...aro.org
Subject: Re: [RFC PATCH v1 00/11] Create fast idle path for short idle periods
> We need a tradeoff here IMHO. I'll check Daniel's work to understand how/if
> it's better than menu governor.
I still would like to see how the fast path without the C1 heuristic works.
Fast pathing is a different concept from a better predictor. IMHO we need
both, but the first is likely lower hanging fruit.
-Andi
Powered by blists - more mailing lists