From: Vincent Guittot <vincent.guittot@linaro.org>
To: peterz@infradead.org, mingo@kernel.org,
linux-kernel@vger.kernel.org, valentin.schneider@arm.com
Cc: morten.rasmussen@foss.arm.com, brendan.jackman@arm.com,
dietmar.eggemann@arm.com,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: [PATCH v4 0/3] sched: Update blocked load
Date: Tue, 13 Feb 2018 11:31:16 +0100 [thread overview]
Message-ID: <1518517879-2280-1-git-send-email-vincent.guittot@linaro.org> (raw)
This patchset applies on top of Peter's sched/esting branch minus the last 2 commit:
56eb46798b33 ("sched: Clean up nohz enter/exit")
v4:
- fixed some compilation issues raised by kbuild
- update comments
- reorder condition tests for calling _nohz_idle_balance in newly_idle case
in order to make it more readable
v3:
- add memory barrier
- add comments
v2:
- minor naming updates
Vincent Guittot (3):
sched: Stop nohz stats when decayed
sched: reduce the periodic update duration
sched: update blocked load when newly idle
kernel/sched/fair.c | 453 ++++++++++++++++++++++++++++++++++-----------------
kernel/sched/sched.h | 1 +
2 files changed, 305 insertions(+), 149 deletions(-)
--
2.7.4
next reply other threads:[~2018-02-13 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 10:31 Vincent Guittot [this message]
2018-02-13 10:31 ` [PATCH v4 1/3] sched: Stop nohz stats when decayed Vincent Guittot
2018-03-09 9:03 ` [tip:sched/core] sched/nohz: Stop NOHZ " tip-bot for Vincent Guittot
2018-02-13 10:31 ` [PATCH v4 2/3] sched: reduce the periodic update duration Vincent Guittot
2018-03-09 9:04 ` [tip:sched/core] sched/fair: Reduce " tip-bot for Vincent Guittot
2018-02-13 10:31 ` [PATCH 3/3] sched: update blocked load when newly idle Vincent Guittot
2018-02-14 14:40 ` Valentin Schneider
2018-02-14 14:43 ` Vincent Guittot
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=1518517879-2280-1-git-send-email-vincent.guittot@linaro.org \
--to=vincent.guittot@linaro.org \
--cc=brendan.jackman@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@foss.arm.com \
--cc=peterz@infradead.org \
--cc=valentin.schneider@arm.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;
as well as URLs for NNTP newsgroup(s).