From: Juri Lelli <juri.lelli@arm.com>
To: "peterz@infradead.org" <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] sched fixes and clean-ups
Date: Fri, 18 Sep 2015 10:02:59 +0100 [thread overview]
Message-ID: <55FBD343.7060908@arm.com> (raw)
In-Reply-To: <1441188096-23021-1-git-send-email-juri.lelli@arm.com>
Hi Peter,
On 02/09/15 11:01, Juri Lelli wrote:
> Hi all,
>
> while trying to come up with 01/04, I collected the following set of fixes.
>
> Patches 02-04/04 are simple refactoring of code and clean-ups.
> Patch 01/04 is instead my attempt to fix a problem highlighted some time
> back by Wanpeng Li regarding hotplug and the way SCHED_DEADLINE keeps
> track of admission control decisions (admitted bandwidth). This patch
> is invasive, but it seems to fix the problem (and I couldn't find
> cleaner fixes :-/). Please give special attention to it :-).
>
What about the other three fixes?
Thanks!
- Juri
> Thanks!
>
> Best,
>
> - Juri
>
> Juri Lelli (4):
> sched/{cpuset,core}: restore complete root_domain status across
> hotplug
> sched/deadline: unify dl_time_before usage
> locking/rtmutex: fix open coded check in rt_mutex_waiter_less()
> sched/rt: make (do_)balance_runtime() return void
>
> include/linux/sched.h | 2 ++
> include/linux/sched/deadline.h | 5 +++++
> kernel/cpuset.c | 41 +++++++++++++++++++++++++++++++++++++++++
> kernel/locking/rtmutex.c | 3 ++-
> kernel/sched/core.c | 17 +++++++++++++++++
> kernel/sched/cpudeadline.c | 5 -----
> kernel/sched/cpudeadline.h | 1 +
> kernel/sched/rt.c | 22 ++++++----------------
> kernel/sched/sched.h | 5 -----
> 9 files changed, 74 insertions(+), 27 deletions(-)
>
prev parent reply other threads:[~2015-09-18 9:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 10:01 [PATCH 0/4] sched fixes and clean-ups Juri Lelli
2015-09-02 10:01 ` [PATCH 1/4] sched/{cpuset,core}: restore complete root_domain status across hotplug Juri Lelli
2015-09-09 15:11 ` Peter Zijlstra
2015-09-10 9:03 ` Juri Lelli
2015-09-02 10:01 ` [PATCH 2/4] sched/deadline: unify dl_time_before usage Juri Lelli
2015-09-23 8:46 ` [tip:sched/core] sched/deadline: Unify dl_time_before() usage tip-bot for Juri Lelli
2015-09-02 10:01 ` [PATCH 3/4] locking/rtmutex: fix open coded check in rt_mutex_waiter_less() Juri Lelli
2015-09-23 8:47 ` [tip:sched/core] sched/deadline, locking/rtmutex: Fix " tip-bot for Juri Lelli
2015-09-02 10:01 ` [PATCH 4/4] sched/rt: make (do_)balance_runtime() return void Juri Lelli
2015-09-23 8:47 ` [tip:sched/core] sched/rt: Make " tip-bot for Juri Lelli
2015-09-18 9:02 ` Juri Lelli [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=55FBD343.7060908@arm.com \
--to=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/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