From: Juri Lelli <juri.lelli@arm.com>
To: peterz@infradead.org
Cc: mingo@redhat.com, juri.lelli@gmail.com, raistlin@linux.it,
michael@amarulasolutions.com, fchecconi@gmail.com,
daniel.wagner@bmw-carit.de, vincent@legout.info,
luca.abeni@unitn.it, linux-kernel@vger.kernel.org,
Juri Lelli <juri.lelli@arm.com>
Subject: [PATCH 0/3] SCHED_DEADLINE fix AC and SMP scheduling
Date: Fri, 19 Sep 2014 10:22:38 +0100 [thread overview]
Message-ID: <1411118561-26323-1-git-send-email-juri.lelli@arm.com> (raw)
Hello everyone,
This patchset fixes admission control, bandwidth management and
(clustered) SMP scheduling for SCHED_DEADLINE tasks.
Patch 1/3 properly clears things up when a task leaves SCHED_DEADLINE,
without dying (and it is a different solution for the problem spotted
by Daniel, http://marc.info/?l=linux-kernel&m=140974782707197&w=2);
patch 2/3 fixes how cpusets bandwidth is checked and updated; patch 3/3
fixes SMP (clustered) scheduling.
Best Regards,
- Juri
Juri Lelli (3):
sched/deadline: clear dl_entity params when setscheduling to different
class
sched/deadline: fix bandwidth check/update when migrating tasks
between exclusive cpusets
sched/deadline: fix inter- exclusive cpusets migrations
include/linux/sched.h | 2 ++
kernel/cpuset.c | 13 ++-----
kernel/sched/core.c | 89 ++++++++++++++++++++++++++++++++++------------
kernel/sched/cpudeadline.c | 4 +--
kernel/sched/deadline.c | 34 ++++++++++++++++--
kernel/sched/sched.h | 22 ++++++++++++
6 files changed, 125 insertions(+), 39 deletions(-)
--
2.1.0
next reply other threads:[~2014-09-19 9:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 9:22 Juri Lelli [this message]
2014-09-19 9:22 ` [PATCH 1/3] sched/deadline: clear dl_entity params when setscheduling to different class Juri Lelli
2014-09-19 11:44 ` Daniel Wagner
2014-09-19 12:43 ` Juri Lelli
2014-09-22 18:50 ` Vincent Legout
2014-09-24 14:54 ` [tip:sched/core] sched/deadline: Clear " tip-bot for Juri Lelli
2014-10-08 12:32 ` [PATCH 1/3] sched/deadline: clear " Wanpeng Li
2014-10-21 12:15 ` Wanpeng Li
2014-10-21 13:15 ` Juri Lelli
2014-09-19 9:22 ` [PATCH 2/3] sched/deadline: fix bandwidth check/update when migrating tasks between exclusive cpusets Juri Lelli
2014-09-19 11:47 ` Daniel Wagner
2014-09-19 12:46 ` Juri Lelli
2014-09-19 21:25 ` Peter Zijlstra
2014-09-23 8:12 ` Juri Lelli
2014-10-07 8:59 ` Juri Lelli
2014-10-07 12:31 ` Peter Zijlstra
2014-10-07 13:12 ` Juri Lelli
2014-10-28 11:07 ` [tip:sched/core] sched/deadline: Ensure that updates to exclusive cpusets don't break AC tip-bot for Juri Lelli
2014-09-22 19:24 ` [PATCH 2/3] sched/deadline: fix bandwidth check/update when migrating tasks between exclusive cpusets Vincent Legout
2014-09-23 8:09 ` Juri Lelli
2014-09-23 13:08 ` Daniel Wagner
2014-10-28 11:07 ` [tip:sched/core] sched/deadline: Fix bandwidth check/ update " tip-bot for Juri Lelli
2014-09-19 9:22 ` [PATCH 3/3] sched/deadline: fix inter- exclusive cpusets migrations Juri Lelli
2014-09-24 14:55 ` [tip:sched/core] sched/deadline: Fix " tip-bot for Juri Lelli
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=1411118561-26323-1-git-send-email-juri.lelli@arm.com \
--to=juri.lelli@arm.com \
--cc=daniel.wagner@bmw-carit.de \
--cc=fchecconi@gmail.com \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@unitn.it \
--cc=michael@amarulasolutions.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=raistlin@linux.it \
--cc=vincent@legout.info \
/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).