From: Rik van Riel <riel@redhat.com>
To: Youquan Song <youquan.song@linux.intel.com>
Cc: Linux kernel Mailing List <linux-kernel@vger.kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Boris Ostrovsky <boris.ostrovsky@amd.com>,
Len Brown <len.brown@intel.com>,
Deepthi Dharwar <deepthi@linux.vnet.ibm.com>,
ShuoX Liu <shuox.liu@intel.com>,
youquan.song@intel.com
Subject: Re: KS/Plumbers: c-state governor BOF
Date: Tue, 11 Sep 2012 12:24:07 -0400 [thread overview]
Message-ID: <504F65A7.3040203@redhat.com> (raw)
In-Reply-To: <20120912041547.GB23544@linux-youquan.bj.intel.com>
On 09/12/2012 12:15 AM, Youquan Song wrote:
>> Your patches could make a lot of sense when integrated with my
>> patches:
>>
>> http://people.redhat.com/riel/cstate/
>> However, we should probably get the tracepoint upstream first,
>> so we can know for sure :)
>
> I can not access the patches at this directory. Can you send it to me?
> I will look at your patches and then integrated with my patches to look
> what will happen tomorrow.
Argh, fixed!
> Do you have test case share? or ideas how to show the benefit.
>
> I have done many test for my pathes. It show some benefit big or small
> in various cases, but there is no negative effect showed at least.
>
> I have two onviced test cases to show the great benefit
> 1. turbostat v1 (before 3.5)
> 2. I write the simple test application which also show greate benefit.
> running it by #./idle_predict -l 8
>
>
> I write a simple application using usleep which it is clear to the
> repeat mode prediction failure will greatly effect the application with
> such repeat pattern.
Your test looks exactly like the kind of thing that could benefit
from my changes to the menu governor :)
--
All rights reversed
prev parent reply other threads:[~2012-09-11 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 17:01 KS/Plumbers: c-state governor BOF Rik van Riel
2012-08-29 20:41 ` Rik van Riel
2012-09-12 2:43 ` Youquan Song
2012-09-11 15:34 ` Rik van Riel
2012-09-12 4:15 ` Youquan Song
2012-09-11 16:24 ` Rik van Riel [this message]
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=504F65A7.3040203@redhat.com \
--to=riel@redhat.com \
--cc=arjan@linux.intel.com \
--cc=boris.ostrovsky@amd.com \
--cc=deepthi@linux.vnet.ibm.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=shuox.liu@intel.com \
--cc=youquan.song@intel.com \
--cc=youquan.song@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox