lkml.org 
[lkml]   [2020]   [Feb]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Date
From
SubjectRe: [PATCH 3/3] sched/rt: fix pushing unfit tasks to a better CPU
Hi Qais,

On Fri, Feb 14, 2020 at 04:39:49PM +0000, Qais Yousef wrote:

[...]

> diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
> index 0c8bac134d3a..5ea235f2cfe8 100644
> --- a/kernel/sched/rt.c
> +++ b/kernel/sched/rt.c
> @@ -1430,7 +1430,7 @@ select_task_rq_rt(struct task_struct *p, int cpu, int sd_flag, int flags)
> {
> struct task_struct *curr;
> struct rq *rq;
> - bool test;
> + bool test, fit;
>
> /* For anything but wake ups, just return the task_cpu */
> if (sd_flag != SD_BALANCE_WAKE && sd_flag != SD_BALANCE_FORK)
> @@ -1471,16 +1471,32 @@ select_task_rq_rt(struct task_struct *p, int cpu, int sd_flag, int flags)
> unlikely(rt_task(curr)) &&
> (curr->nr_cpus_allowed < 2 || curr->prio <= p->prio);
>
> - if (test || !rt_task_fits_capacity(p, cpu)) {
> + fit = rt_task_fits_capacity(p, cpu);
> +
> + if (test || !fit) {
> int target = find_lowest_rq(p);
>
> - /*
> - * Don't bother moving it if the destination CPU is
> - * not running a lower priority task.
> - */
> - if (target != -1 &&
> - p->prio < cpu_rq(target)->rt.highest_prio.curr)
> - cpu = target;
> + if (target != -1) {
> + /*
> + * Don't bother moving it if the destination CPU is
> + * not running a lower priority task.
> + */
> + if (p->prio < cpu_rq(target)->rt.highest_prio.curr) {
> +
> + cpu = target;
> +
> + } else if (p->prio == cpu_rq(target)->rt.highest_prio.curr) {
> +
> + /*
> + * If the priority is the same and the new CPU
> + * is a better fit, then move, otherwise don't
> + * bother here either.
> + */
> + fit = rt_task_fits_capacity(p, target);
> + if (fit)
> + cpu = target;
> + }
> + }

I understand that we are opting for the migration when priorities are tied but
the task can fit on the new task. But there is no guarantee that this task
stay there. Because any CPU that drops RT prio can pull the task. Then why
not leave it to the balancer?

I notice a case where tasks would migrate for no reason (happens without this
patch also). Assuming BIG cores are busy with other RT tasks. Now this RT
task can go to *any* little CPU. There is no bias towards its previous CPU.
I don't know if it makes any difference but I see RT task placement is too
keen on reducing the migrations unless it is absolutely needed.

Thanks,
Pavan

--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.

\
 
 \ /
  Last update: 2020-02-17 10:23    [W:0.168 / U:3.192 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site