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



> 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.

Sadly, I‘m travelling at the moment, I‘m not able to do something till december.

> 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/
> 
> --
> 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-17 16:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=391401416243011@web3h.yandex.ru \
    --to=tkhai@yandex.ru \
    --cc=juri.lelli@arm.com \
    --cc=ktkhai@parallels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=wanpeng.li@linux.intel.com \
    /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