[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130613214007.GA32127@pd.tnic>
Date: Thu, 13 Jun 2013 23:40:08 +0200
From: Borislav Petkov <bp@...en8.de>
To: Stratos Karafotis <stratosk@...aphore.gr>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>, Borislav Petkov <bp@...e.de>,
Viresh Kumar <viresh.kumar@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, linux-pm@...r.kernel.org,
cpufreq@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/3] cpufreq: ondemand: Change the calculation of
target frequency
On Fri, Jun 14, 2013 at 12:22:18AM +0300, Stratos Karafotis wrote:
> Please let me share some more test results using aim9 benchmark suite:
> https://docs.google.com/spreadsheet/ccc?key=0AnMfNYUV1k0ddDdGdlJyUHpqT2xGY1lBOEt2UEVnNlE&usp=sharing
>
> Each test was running for 10sec.
> Total execution time with and without the patch was almost identical, which is
> expected since the tests in aim9 run for a specific period.
> The energy during the test run was increased by 0.43% with the patch.
> The performance was increased by 1.25% (average) with this patch.
Not bad. However, exec_test and fork_test are kinda unexpected with such
a high improvement percentage. Happen to have an explanation?
FWIW, if we don't find any serious perf/power regressions with
this patch, I'd say it is worth applying even solely for the code
simplification it brings.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
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