public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wanpeng Li <wanpeng.li@linux.intel.com>
To: Kirill Tkhai <ktkhai@parallels.com>
Cc: Wanpeng Li <wanpeng.li@linux.intel.com>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@arm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] sched/deadline: support dl task migration during cpu hotplug
Date: Mon, 17 Nov 2014 06:59:14 +0800	[thread overview]
Message-ID: <20141116225914.GA6951@kernel> (raw)
In-Reply-To: <1415874091.15631.44.camel@tkhai>

Hi Kirill,
On Thu, Nov 13, 2014 at 01:21:31PM +0300, Kirill Tkhai wrote:
>> >>>> @@ -1185,8 +1223,9 @@ 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);
>> >>>> +	cpumask_copy(later_mask, cpu_active_mask);
>> >>>> +	if (likely(task_rq(task)->online))
>> >>>> +		cpumask_and(later_mask, later_mask, task_rq(task)->rd->span);
>> >>>>   	cpumask_and(later_mask, later_mask, &task->cpus_allowed);
>> >>>>   	best_cpu = cpudl_find(&task_rq(task)->rd->cpudl,
>> >>>>   			task, later_mask);
>> > Also, we should think about the following situation.
>> >
>> > DL task is left on dead rq. In your scheme it will be moved by the timer.
>> > But what will be if somebody changes the class of the task (before timer)?
>> 
>> I think timer will be cancelled in switched_from_dl().
>
>Yeah, but nobody will move this task to alive rq.
>
>> 
>> Regards,
>> Wanpeng Li
>> 
>> > In this case the task still remains on dead rq.
>> >
>> > We should handle this situation in some way.

Your proposal is a great appreciated. 

Regards,
Wanpeng Li 

>> >
>> > Kirill
>> >
>> >
>> > --
>> > 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/
>> 
>

  reply	other threads:[~2014-11-16 23:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12  1:06 [PATCH v5] sched/deadline: support dl task migration during cpu hotplug Wanpeng Li
2014-11-12 15:08 ` Juri Lelli
2014-11-12 15:39   ` Peter Zijlstra
2014-11-12 23:02     ` Wanpeng Li
2015-01-05 14:52     ` Peter Zijlstra
2015-01-06  2:14       ` Wanpeng Li
2014-11-12 23:22   ` Wanpeng Li
2014-11-18 23:18   ` Wanpeng Li
2014-11-19 10:13     ` Juri Lelli
2014-11-19 12:30       ` Wanpeng Li
2014-11-19 13:49         ` Juri Lelli
2014-11-19 23:08           ` Wanpeng Li
2014-11-12 16:27 ` Kirill Tkhai
2014-11-12 22:56   ` Wanpeng Li
2014-11-13 10:10     ` Kirill Tkhai
2014-11-13 10:19       ` Wanpeng Li
2014-11-13 10:21         ` Kirill Tkhai
2014-11-16 22:59           ` Wanpeng Li [this message]
2014-11-20  8:49           ` 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=20141116225914.GA6951@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox