[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160119175038.GS6588@sirena.org.uk>
Date: Tue, 19 Jan 2016 17:50:38 +0000
From: Mark Brown <broonie@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Juri Lelli <juri.lelli@....com>, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
vincent.guittot@...aro.org, robh+dt@...nel.org,
mark.rutland@....com, linux@....linux.org.uk, sudeep.holla@....com,
lorenzo.pieralisi@....com, catalin.marinas@....com,
will.deacon@....com, morten.rasmussen@....com,
dietmar.eggemann@....com
Subject: Re: [RFC PATCH v2 0/4] CPUs capacity information for heterogeneous
systems
On Tue, Jan 19, 2016 at 04:05:51PM +0100, Peter Zijlstra wrote:
> On Fri, Jan 08, 2016 at 02:09:28PM +0000, Juri Lelli wrote:
> > cons: - not easy to come up with a clean solution, as it seems interaction
> > with several subsystems (e.g., cpufreq) is required
> > - not easy to agree upon a single benchmark (that has to be both
> > representative and simple enough to run at boot)
> > - numbers might (and do) vary from boot to boot
> This last point is a total pain for benchmarking, it means nothing is
> every reproducible.
> Therefore, I would always augment the above (2) with the below (3), such
> that you can overwrite the results with a known stable set of numbers:
The suggestion when the previous version was being discussed was that
there are supposed to be some other knobs one uses for tuning and one
was never supposed to use these numbers.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists