From: Stratos Karafotis <stratosk@semaphore.gr>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 linux-next] cpufreq: ondemand: Calculate gradient of CPU load to early increase frequency
Date: Tue, 16 Apr 2013 21:34:21 +0300 [thread overview]
Message-ID: <516D99AD.4070104@semaphore.gr> (raw)
In-Reply-To: <CAKohponhGA1LCe8Hv7xHk0ULXVVPTgmEY-nKTgpE0w6VmX--Ng@mail.gmail.com>
On 04/10/2013 06:22 AM, Viresh Kumar wrote:
> On 9 April 2013 22:26, Stratos Karafotis <stratosk@semaphore.gr> wrote:
>> On 04/05/2013 10:50 PM, Stratos Karafotis wrote:
>>>
>>> Hi Viresh,
>>>
>>> On 04/04/2013 07:54 AM, Viresh Kumar wrote:
>>>>
>>>> Hi Stratos,
>>>>
>>>> Yes, your results show some improvements. BUT if performance is the only
>>>> thing
>>>> we were looking for, then we will never use ondemand governor but
>>>> performance
>>>> governor.
>>>>
>>>> I suspect this little increase in performance must have increased power
>>>> numbers
>>>> too (significantly). So, if you can get numbers in the form of
>>>> power/performance
>>>> with and without your patch, it will be great.
>>>>
>>>> --
>>>> viresh
>>>>
>>>
>>> I run some more tests. I increased the number of iterations to 100 (from
>>> 20).
>>> I also test for counter 1,000,000 (~4200us), 5,000,000 (~10000us),
>>> 15,000,000 (~30000us).
>>>
>>> This time, I also extracted statistics from cpufreq_stats driver. I think
>>> this will be an
>>> indication for power consumption. Below the results and attached the
>>> program I used for to
>>> get these numbers.
>>
>>
>> Any comments would be appreciated.
>
> Sorry, i forgot about this mail earlier..
>
> Your performance numbers look improved but i am still not sure about
> power consumption. But as this is not going to be the default settings, i
> think we can take this patch.
>
> @Rafael:?
>
Hi Rafael,
I'm sorry for bothering you again for this patch.
Are these number adequate? Should I provide more benchmark results?
Thanks for your time.
Stratos
next prev parent reply other threads:[~2013-04-16 18:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 6:31 [PATCH v3 linux-next] cpufreq: ondemand: Calculate gradient of CPU load to early increase frequency stratosk
2013-04-03 6:31 ` stratosk
2013-04-03 6:43 ` Viresh Kumar
2013-04-03 11:14 ` Rafael J. Wysocki
2013-04-03 23:30 ` Stratos Karafotis
2013-04-04 4:54 ` Viresh Kumar
2013-04-05 19:50 ` Stratos Karafotis
2013-04-09 16:56 ` Stratos Karafotis
2013-04-10 3:22 ` Viresh Kumar
2013-04-16 18:34 ` Stratos Karafotis [this message]
2013-04-26 14:41 ` Stratos Karafotis
-- strict thread matches above, loose matches on Subject: below --
2013-04-04 7:21 stratosk
2013-04-04 7:21 ` stratosk
2013-04-04 6:47 stratosk
2013-04-04 6:47 ` stratosk
2013-04-04 6:51 ` Viresh Kumar
2013-02-20 20:50 [PATCH " Stratos Karafotis
2013-02-21 4:59 ` Viresh Kumar
2013-02-21 11:31 ` [PATCH v2 " Stratos Karafotis
2013-02-21 15:33 ` Viresh Kumar
2013-02-21 17:39 ` [PATCH v3 " Stratos Karafotis
2013-02-22 1:56 ` Viresh Kumar
2013-02-22 5:57 ` Viresh Kumar
2013-02-22 12:47 ` Rafael J. Wysocki
2013-03-29 22:27 ` Stratos Karafotis
2013-03-29 22:38 ` Rafael J. Wysocki
2013-04-02 13:50 ` Rafael J. Wysocki
2013-04-02 15:49 ` Stratos Karafotis
2013-04-02 22:55 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=516D99AD.4070104@semaphore.gr \
--to=stratosk@semaphore.gr \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.