Re: [PATCH v2 2/2] cpufreq: powernv: Ramp-down global pstate slower than local-pstate

2016-04-20 Thread Stewart Smith
Akshay Adiga writes: > Iozone results show fairly consistent performance boost. > YCSB on redis shows improved Max latencies in most cases. What about power consumption? > Iozone write/rewite test were made with filesizes 200704Kb and 401408Kb > with different record sizes . The following table

Re: [PATCH v2 2/2] cpufreq: powernv: Ramp-down global pstate slower than local-pstate

2016-04-19 Thread Akshay Adiga
Hi Viresh, On 04/18/2016 03:48 PM, Viresh Kumar wrote: On 15-04-16, 11:58, Akshay Adiga wrote: static int powernv_cpufreq_reboot_notifier(struct notifier_block *nb, - unsigned long action, void *unused) + unsigned long act

Re: [PATCH v2 2/2] cpufreq: powernv: Ramp-down global pstate slower than local-pstate

2016-04-18 Thread Viresh Kumar
On 15-04-16, 11:58, Akshay Adiga wrote: > static int powernv_cpufreq_reboot_notifier(struct notifier_block *nb, > - unsigned long action, void *unused) > +unsigned long action, void *unused) Unrelated change.. better don't add su

[PATCH v2 2/2] cpufreq: powernv: Ramp-down global pstate slower than local-pstate

2016-04-14 Thread Akshay Adiga
The frequency transition latency from pmin to pmax is observed to be in few millisecond granurality. And it usually happens to take a performance penalty during sudden frequency rampup requests. This patch set solves this problem by using an entity called "global pstates". The global pstate is a C