From: Wanpeng Li <wanpeng.li@linux.intel.com>
To: Kirill Tkhai <ktkhai@parallels.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@arm.com>,
linux-kernel@vger.kernel.org,
Wanpeng Li <wanpeng.li@linux.intel.com>
Subject: Re: [PATCH v4] sched/deadline: support dl task migration during cpu hotplug
Date: Wed, 12 Nov 2014 07:53:20 +0800 [thread overview]
Message-ID: <20141111235320.GA3946@kernel> (raw)
In-Reply-To: <1415711354.15631.15.camel@tkhai>
Hi Kirill,
On Tue, Nov 11, 2014 at 04:09:14PM +0300, Kirill Tkhai wrote:
>В Вт, 11/11/2014 в 21:07 +0800, Wanpeng Li пишет:
>> Hi Kirill,
>> On 11/11/14, 7:10 PM, Kirill Tkhai wrote:
>> > В Вт, 11/11/2014 в 10:30 +0800, Wanpeng Li пишет:
>> >> I observe that dl task can't be migrated to other cpus during cpu hotplug, in
>> >> addition, task may/may not be running again if cpu is added back. The root cause
>> >> which I found is that dl task will be throtted and removed from dl rq after
>> >> comsuming all budget, which leads to stop task can't pick it up from dl rq and
>> >> migrate to other cpus during hotplug.
>> >>
>> >> The method to reproduce:
>> >> schedtool -E -t 50000:100000 -e ./test
>> >> Actually test is just a simple for loop. Then observe which cpu the test
>> >> task is on.
>> >> echo 0 > /sys/devices/system/cpu/cpuN/online
>> >>
>> >> This patch fix it by push the task to another cpu in dl_task_timer() if
>> >> rq is offline.
>> >>
>> >> Signed-off-by: Wanpeng Li <wanpeng.li@linux.intel.com>
>> > I'm still thinking we don't have to guarantee any "deadlines" during cpu hotplug...
>> > But, if speaking about this way:
>> >
>> >> ---
>> >> v3 -> v4:
>> >> * use tsk_cpus_allowed wrapper
>> >> * fix compile error
>> >> v2 -> v3:
>> >> * don't get_task_struct
>> >> * if cannot preempt any rq, fallback to pick any online cpus
>> >> * use cpu_active_mask as original later_mask if cpu is offline
>> >> v1 -> v2:
>> >> * push the task to another cpu in dl_task_timer() if rq is offline.
>> >>
>> >>
>> >> kernel/sched/deadline.c | 51 ++++++++++++++++++++++++++++++++++++++++++++++---
>> >> 1 file changed, 48 insertions(+), 3 deletions(-)
>> >>
>> >> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
>> >> index 00324af..e0fbba4 100644
>> >> --- a/kernel/sched/deadline.c
>> >> +++ b/kernel/sched/deadline.c
>> >> @@ -487,6 +487,7 @@ static int start_dl_timer(struct sched_dl_entity *dl_se, bool boosted)
>> >> return hrtimer_active(&dl_se->dl_timer);
>> >> }
>> >>
>> >> +static struct rq *find_lock_later_rq(struct task_struct *task, struct rq *rq);
>> >> /*
>> >> * This is the bandwidth enforcement timer callback. If here, we know
>> >> * a task is not on its dl_rq, since the fact that the timer was running
>> >> @@ -538,6 +539,46 @@ again:
>> >> update_rq_clock(rq);
>> >> dl_se->dl_throttled = 0;
>> >> dl_se->dl_yielded = 0;
>> >> +
>> >> + /*
>> >> + * So if we find that the rq the task was on is no longer
>> >> + * available, we need to select a new rq.
>> >> + */
>> >> + if (!rq->online) {
>> >> + struct rq *later_rq = NULL;
>> >> +
>> >> + raw_spin_unlock(&rq->lock);
>> >> +
>> >> + later_rq = find_lock_later_rq(p, rq);
>> > find_lock_later_rq() expects that rq is locked.
>> >
>> > The comment near its head confuses a reader. It locks newly found rq.
>>
>> Sorry for my bad, what's you think should be changed?
>
>raw_spin_unlock(&rq->lock) is wrong here. It's not need.
>
The machine down after remove this.
Regards,
Wanpeng Li
>>
>> >
>> >> +
>> >> + if (!later_rq) {
>> >> + int cpu;
>> >> +
>> >> + /*
>> >> + * If cannot preempt any rq, fallback to pick any
>> >> + * online cpu.
>> >> + */
>> >> + for_each_cpu(cpu, tsk_cpus_allowed(p))
>> >> + if (cpu_online(cpu))
>> >> + later_rq = cpu_rq(cpu);
>> >> + if (!later_rq) {
>> >> + pr_warn("fail to find any online and task "
>> >> + "will never come back to us\n");
>> >> + goto out;
>> >> + }
>> >> + }
>> >> +
>> >> + deactivate_task(rq, p, 0);
>> >> + set_task_cpu(p, later_rq->cpu);
>> >> + activate_task(later_rq, p, 0);
>> >> +
>> >> + resched_curr(later_rq);
>> >> +
>> >> + double_unlock_balance(rq, later_rq);
>> > double_unlock_balance() unlocks later_rq only.
>> >
>> >> +
>> >> + goto out;
>> >> + }
>> >> +
>> >> if (task_on_rq_queued(p)) {
>> >> enqueue_task_dl(rq, p, ENQUEUE_REPLENISH);
>> >> if (dl_task(rq->curr))
>> >> @@ -555,7 +596,7 @@ again:
>> >> }
>> >> unlock:
>> >> raw_spin_unlock(&rq->lock);
>> >> -
>> >> +out:
>> >> return HRTIMER_NORESTART;
>> >> }
>> >>
>> >> @@ -1185,8 +1226,12 @@ static int find_later_rq(struct task_struct *task)
>> >> * We have to consider system topology and task affinity
>> >> * first, then we can look for a suitable cpu.
>> >> */
>> >> - cpumask_copy(later_mask, task_rq(task)->rd->span);
>> >> - cpumask_and(later_mask, later_mask, cpu_active_mask);
>> >> + if (likely(task_rq(task)->online)) {
>> >> + cpumask_copy(later_mask, task_rq(task)->rd->span);
>> >> + cpumask_and(later_mask, later_mask, cpu_active_mask);
>> >> + } else
>> >> + /* for offline cpus we have a singleton rd */
>> >> + cpumask_copy(later_mask, cpu_active_mask);
>> >> cpumask_and(later_mask, later_mask, &task->cpus_allowed);
>> >> best_cpu = cpudl_find(&task_rq(task)->rd->cpudl,
>> >> task, later_mask);
>> >
>> > --
>> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> > the body of a message to majordomo@vger.kernel.org
>> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>> > Please read the FAQ at http://www.tux.org/lkml/
>>
>
next prev parent reply other threads:[~2014-11-12 0:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 2:30 [PATCH v4] sched/deadline: support dl task migration during cpu hotplug Wanpeng Li
2014-11-11 11:10 ` Kirill Tkhai
2014-11-11 13:07 ` Wanpeng Li
2014-11-11 13:09 ` Kirill Tkhai
2014-11-11 23:53 ` Wanpeng Li [this message]
2014-11-12 0:12 ` 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=20141111235320.GA3946@kernel \
--to=wanpeng.li@linux.intel.com \
--cc=juri.lelli@arm.com \
--cc=ktkhai@parallels.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.