From: Rik van Riel <riel@surriel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux PM <linux-pm@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.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>,
Doug Smythies <dsmythies@telus.net>,
Aubrey Li <aubrey.li@linux.intel.com>,
Mike Galbraith <mgalbraith@suse.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] cpuidle: poll_state: Add time limit to poll_idle()
Date: Thu, 22 Mar 2018 13:19:16 -0400 [thread overview]
Message-ID: <1521739156.6308.30.camel@surriel.com> (raw)
In-Reply-To: <4731938.EeADOapqQb@aspire.rjw.lan>
[-- Attachment #1: Type: text/plain, Size: 2797 bytes --]
On Thu, 2018-03-22 at 18:09 +0100, Rafael J. Wysocki wrote:
> On Thursday, March 22, 2018 5:32:23 PM CET Rik van Riel wrote:
> > On Wed, 2018-03-14 at 15:08 +0100, Rafael J. Wysocki wrote:
> > > From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > >
> > > If poll_idle() is allowed to spin until need_resched() returns
> > > 'true',
> > > it may actually spin for a much longer time than expected by the
> > > idle
> > > governor, since set_tsk_need_resched() is not always called by
> > > the
> > > timer interrupt handler. If that happens, the CPU may spend much
> > > more time than anticipated in the "polling" state.
> > >
> > > To prevent that from happening, limit the time of the spinning
> > > loop
> > > in poll_idle().
> > >
> > > Suggested-by: Peter Zijlstra <peterz@infradead.org>
> > > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> >
> > So ... about bisecting that other patch series...
> >
> > It turned out I had this patch, which looks so
> > obviously correct, as patch #1 in my series.
> >
> > It also turned out that this patch is responsible
> > for the entire 5-10% increase in CPU use for the
> > memcache style workload.
> >
> > I wonder if keeping an idle HT thread much busier
> > than before slows down its sibling, or something
> > like that.
>
> Uhm, sorry about this.
No worries, this is why we do patch reviews and
tests in the first place.
> Does it improve if you do something like the below on top of it?
That was my next thing to try, after testing just
the idle nohz series by itself :)
I'll push both into the test systems, and will
get back to you when I have answers.
> > Let me go test the nohz idle series by itself,
> > without this patch.
>
> OK
>
> ---
> drivers/cpuidle/poll_state.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> Index: linux-pm/drivers/cpuidle/poll_state.c
> ===================================================================
> --- linux-pm.orig/drivers/cpuidle/poll_state.c
> +++ linux-pm/drivers/cpuidle/poll_state.c
> @@ -10,6 +10,7 @@
> #include <linux/sched/idle.h>
>
> #define POLL_IDLE_TIME_LIMIT (TICK_NSEC / 16)
> +#define POLL_IDLE_COUNT 1000
>
> static int __cpuidle poll_idle(struct cpuidle_device *dev,
> struct cpuidle_driver *drv, int
> index)
> @@ -18,9 +19,14 @@ static int __cpuidle poll_idle(struct cp
>
> local_irq_enable();
> if (!current_set_polling_and_test()) {
> + unsigned int loop_count = 0;
> +
> while (!need_resched()) {
> cpu_relax();
> + if (loop_count++ < POLL_IDLE_COUNT)
> + continue;
>
> + loop_count = 0;
> if (local_clock() - time_start >
> POLL_IDLE_TIME_LIMIT)
> break;
> }
>
>
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-03-22 17:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 14:08 [PATCH v3] cpuidle: poll_state: Add time limit to poll_idle() Rafael J. Wysocki
2018-03-22 16:32 ` Rik van Riel
2018-03-22 17:09 ` Rafael J. Wysocki
2018-03-22 17:19 ` Rik van Riel [this message]
2018-03-22 17:24 ` Rafael J. Wysocki
2018-03-25 20:15 ` Rik van Riel
2018-03-25 21:34 ` Rafael J. Wysocki
2018-03-25 21:45 ` Rik van Riel
2018-03-26 5:59 ` Doug Smythies
2018-03-26 7:13 ` Doug Smythies
2018-03-26 9:35 ` Rafael J. Wysocki
2018-03-26 16:32 ` Rik van Riel
2018-03-26 21:44 ` Rafael J. Wysocki
2018-03-26 21:48 ` Rik van Riel
2018-03-27 17:59 ` Rik van Riel
2018-03-27 21:06 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2018-03-14 15:00 Doug Smythies
2018-03-20 10:52 ` Rafael J. Wysocki
2018-03-25 0:28 Doug Smythies
2018-03-25 11:53 ` Rafael J. Wysocki
2018-03-25 21:41 ` Rafael J. Wysocki
2018-03-26 6:01 ` Doug Smythies
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=1521739156.6308.30.camel@surriel.com \
--to=riel@surriel.com \
--cc=aubrey.li@linux.intel.com \
--cc=dsmythies@telus.net \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox