From: "Doug Smythies" <dsmythies@telus.net>
To: 'Rik van Riel' <riel@surriel.com>
Cc: 'Linux PM' <linux-pm@vger.kernel.org>,
'Frederic Weisbecker' <fweisbec@gmail.com>,
'Thomas Gleixner' <tglx@linutronix.de>,
'Paul McKenney' <paulmck@linux.vnet.ibm.com>,
'Thomas Ilsche' <thomas.ilsche@tu-dresden.de>,
'Aubrey Li' <aubrey.li@linux.intel.com>,
'Mike Galbraith' <mgalbraith@suse.de>,
'LKML' <linux-kernel@vger.kernel.org>,
'Peter Zijlstra' <peterz@infradead.org>,
"'Rafael J. Wysocki'" <rjw@rjwysocki.net>,
Doug Smythies <dsmythies@telus.net>
Subject: RE: [PATCH v2] cpuidle: poll_state: Add time limit to poll_idle()
Date: Thu, 22 Mar 2018 12:11:33 -0700 [thread overview]
Message-ID: <003f01d3c211$9a094e10$ce1bea30$@net> (raw)
In-Reply-To: z38ge3YFh1Konz38iel45g
On 2018.03.22 09:32 Rik van Riel wrote:
> On Wed, 2018-03-14 at 13:04 +0100, Peter Zijlstra wrote:
>
>> On x86 we don't have to use that time_check_counter thing,
>> sched_clock()
>> is really cheap, not sure if it makes sense on other platforms.
>
> Are you sure? I saw a 5-10% increase in CPU use,
> for a constant query rate to a memcache style
> workload, with v3 of this patch.
I would very much like to be able to repeat your test results.
However, I am not sure what you mean by "memcache style workload".
Is there a test you can point me to? Say a Phoronix type test, for example.
All of my tests with the V3 of this patch have been fine.
... Doug
next prev parent reply other threads:[~2018-03-22 19:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 9:36 [PATCH v2] cpuidle: poll_state: Add time limit to poll_idle() Rafael J. Wysocki
2018-03-14 11:24 ` Rafael J. Wysocki
2018-03-14 12:04 ` Peter Zijlstra
2018-03-14 12:08 ` Rafael J. Wysocki
2018-03-22 16:32 ` Rik van Riel
2018-03-22 19:11 ` Peter Zijlstra
2018-03-27 16:42 ` Rafael J. Wysocki
2018-03-27 18:02 ` Rik van Riel
2018-03-27 21:09 ` Rafael J. Wysocki
2018-03-22 19:11 ` Doug Smythies [this message]
2018-03-23 3:19 ` Doug Smythies
2018-03-23 8:57 ` Rafael J. Wysocki
2018-03-23 9:07 ` Rafael J. Wysocki
2018-03-23 21:30 ` Doug Smythies
2018-03-24 11:25 ` 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='003f01d3c211$9a094e10$ce1bea30$@net' \
--to=dsmythies@telus.net \
--cc=aubrey.li@linux.intel.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mgalbraith@suse.de \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=thomas.ilsche@tu-dresden.de \
/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.