From: Frederic Weisbecker <fweisbec@gmail.com>
To: byungchul.park@lge.com
Cc: mingo@kernel.org, peterz@infradead.org,
linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: [PATCH v4 2/2] sched: consider missed ticks in full NOHZ
Date: Thu, 22 Oct 2015 18:20:33 +0200 [thread overview]
Message-ID: <20151022162031.GA28099@lerouge> (raw)
In-Reply-To: <1444816056-11886-3-git-send-email-byungchul.park@lge.com>
On Wed, Oct 14, 2015 at 06:47:36PM +0900, byungchul.park@lge.com wrote:
> From: Byungchul Park <byungchul.park@lge.com>
>
> Even though the cpu is non-idle when its tick is stoped in full NOHZ,
> current "update_cpu_load" code considers as if the cpu has been idle
> unconditionally. It's wrong. This patch makes the "update_cpu_load"
> code know if the calling path comes from full NOHZ or idle NOHZ.
>
> Signed-off-by: Byungchul Park <byungchul.park@lge.com>
ACK.
Thanks!
next prev parent reply other threads:[~2015-10-22 16:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 9:47 [PATCH v4 0/2] sched: consider missed ticks when updating cpu load byungchul.park
2015-10-14 9:47 ` [PATCH v4 1/2] sched: make __update_cpu_load() handle active tickless case byungchul.park
2015-10-19 13:16 ` Peter Zijlstra
2015-10-20 0:49 ` Byungchul Park
2015-10-20 9:48 ` Peter Zijlstra
2015-10-22 10:28 ` Byungchul Park
2015-10-22 11:05 ` Peter Zijlstra
2015-11-23 16:18 ` [tip:sched/core] sched/fair: Prepare __update_cpu_load() to handle active tickless tip-bot for Byungchul Park
2015-10-14 9:47 ` [PATCH v4 2/2] sched: consider missed ticks in full NOHZ byungchul.park
2015-10-22 16:20 ` Frederic Weisbecker [this message]
2015-11-02 16:10 ` Peter Zijlstra
2015-11-09 2:36 ` Byungchul Park
2015-11-09 10:36 ` Peter Zijlstra
2015-11-09 11:16 ` Byungchul Park
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=20151022162031.GA28099@lerouge \
--to=fweisbec@gmail.com \
--cc=byungchul.park@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.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