From: Wanpeng Li <wanpeng.li@linux.intel.com>
To: Juri Lelli <juri.lelli@arm.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Wanpeng Li <wanpeng.li@linux.intel.com>
Subject: Re: [PATCH 1/7] sched/deadline: fix try to pull pinned dl tasks in pull algorithm
Date: Wed, 15 Apr 2015 07:10:45 +0800 [thread overview]
Message-ID: <20150414231045.GA5831@kernel> (raw)
In-Reply-To: <1428310399-13489-1-git-send-email-wanpeng.li@linux.intel.com>
Ping Juri for this patchset, :)
On Mon, Apr 06, 2015 at 04:53:13PM +0800, Wanpeng Li wrote:
>Function pick_next_earliest_dl_task is used to pick earliest and pushable
>dl task from overloaded cpus in pull algorithm, however, it traverses
>runqueue rbtree instead of pushable task rbtree which is also ordered by
>tasks' deadlines. This will result in getting no candidates from overloaded
>cpus if all the dl tasks on the overloaded cpus are pinned. This patch fix
>it by traversing pushable task rbtree which is also ordered by tasks'
>deadlines.
>
>Signed-off-by: Wanpeng Li <wanpeng.li@linux.intel.com>
>---
> kernel/sched/deadline.c | 29 ++++++++++++++++++++++++++++-
> 1 file changed, 28 insertions(+), 1 deletion(-)
>
>diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
>index 5e95145..b57ceba 100644
>--- a/kernel/sched/deadline.c
>+++ b/kernel/sched/deadline.c
>@@ -1230,6 +1230,33 @@ next_node:
> return NULL;
> }
>
>+/*
>+ * Return the earliest pushable rq's task, which is suitable to be executed
>+ * on the cpu, NULL otherwse
>+ */
>+static struct task_struct *pick_earliest_pushable_dl_task(struct rq *rq,
>+ int cpu)
>+{
>+ struct rb_node *next_node = rq->dl.pushable_dl_tasks_leftmost;
>+ struct task_struct *p = NULL;
>+
>+ if (!has_pushable_dl_tasks(rq))
>+ return NULL;
>+
>+next_node:
>+ if (next_node) {
>+ p = rb_entry(next_node, struct task_struct, pushable_dl_tasks);
>+
>+ if (pick_dl_task(rq, p, cpu))
>+ return p;
>+
>+ next_node = rb_next(next_node);
>+ goto next_node;
>+ }
>+
>+ return NULL;
>+}
>+
> static DEFINE_PER_CPU(cpumask_var_t, local_cpu_mask_dl);
>
> static int find_later_rq(struct task_struct *task)
>@@ -1514,7 +1541,7 @@ static int pull_dl_task(struct rq *this_rq)
> if (src_rq->dl.dl_nr_running <= 1)
> goto skip;
>
>- p = pick_next_earliest_dl_task(src_rq, this_cpu);
>+ p = pick_earliest_pushable_dl_task(src_rq, this_cpu);
>
> /*
> * We found a task to be pulled if:
>--
>1.9.1
next prev parent reply other threads:[~2015-04-14 23:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 8:53 [PATCH 1/7] sched/deadline: fix try to pull pinned dl tasks in pull algorithm Wanpeng Li
2015-04-06 8:53 ` [PATCH 2/7] sched/deadline: make init_sched_dl_class() __init Wanpeng Li
2015-04-07 13:48 ` Juri Lelli
2015-04-07 23:00 ` Wanpeng Li
2015-04-06 8:53 ` [PATCH 3/7] sched/deadline: reduce rq lock contention by eliminating locking of non-feasible target Wanpeng Li
2015-04-07 13:48 ` Juri Lelli
2015-04-07 22:57 ` Wanpeng Li
2015-04-06 8:53 ` [PATCH 4/7] sched/deadline: reschedule if stop task slip in after pull operations Wanpeng Li
2015-04-20 10:27 ` Juri Lelli
2015-04-20 22:59 ` Wanpeng Li
2015-04-20 23:02 ` Wanpeng Li
2015-04-21 8:22 ` Juri Lelli
2015-04-06 8:53 ` [PATCH 5/7] sched/deadline: drop duplicate init_sched_dl_class declaration Wanpeng Li
2015-04-08 8:47 ` Juri Lelli
2015-04-08 8:33 ` Wanpeng Li
2015-04-06 8:53 ` [PATCH 6/7] sched/deadline: depend on clearing throttled status in replenish_dl_entity Wanpeng Li
2015-04-21 8:16 ` Juri Lelli
2015-04-21 8:10 ` Wanpeng Li
2015-04-06 8:53 ` [PATCH 7/7] sched/rt: reschedule if stop/dl task slip in after pull operations Wanpeng Li
2015-04-14 23:10 ` Wanpeng Li [this message]
2015-04-27 9:42 ` [PATCH 1/7] sched/deadline: fix try to pull pinned dl tasks in pull algorithm Wanpeng Li
2015-05-06 7:11 ` Wanpeng Li
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=20150414231045.GA5831@kernel \
--to=wanpeng.li@linux.intel.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).