From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Qais Yousef <qais.yousef@arm.com>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>
Cc: Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sched: rt: Make RT capacity aware
Date: Wed, 30 Oct 2019 12:57:09 +0100 [thread overview]
Message-ID: <39c08971-5d07-8018-915b-9c6284f89d5d@arm.com> (raw)
In-Reply-To: <20191009104611.15363-1-qais.yousef@arm.com>
On 09.10.19 12:46, Qais Yousef wrote:
[...]
> Changes in v2:
> - Use cpupri_find() to check the fitness of the task instead of
> sprinkling find_lowest_rq() with several checks of
> rt_task_fits_capacity().
>
> The selected implementation opted to pass the fitness function as an
> argument rather than call rt_task_fits_capacity() capacity which is
> a cleaner to keep the logical separation of the 2 modules; but it
> means the compiler has less room to optimize rt_task_fits_capacity()
> out when it's a constant value.
I would prefer exporting rt_task_fits_capacity() sched-internally via
kernel/sched/sched.h. Less code changes and the indication whether
rt_task_fits_capacity() has to be used in cpupri_find() is already given
by lowest_mask being !NULL or NULL.
[...]
> +inline bool rt_task_fits_capacity(struct task_struct *p, int cpu)
> +{
> + unsigned int min_cap;
> + unsigned int max_cap;
> + unsigned int cpu_cap;
Nit picking. Since we discussed it already,
I found this "Also please try to aggregate variables of the same type
into a single line. There is no point in wasting screen space::" ;-)
https://lore.kernel.org/r/20181107171149.165693799@linutronix.de
[...]
> @@ -2223,7 +2273,10 @@ static void switched_to_rt(struct rq *rq, struct task_struct *p)
> */
> if (task_on_rq_queued(p) && rq->curr != p) {
> #ifdef CONFIG_SMP
> - if (p->nr_cpus_allowed > 1 && rq->rt.overloaded)
> + bool need_to_push = rq->rt.overloaded ||
> + !rt_task_fits_capacity(p, cpu_of(rq));
> +
> + if (p->nr_cpus_allowed > 1 && need_to_push)
> rt_queue_push_tasks(rq);
> #endif /* CONFIG_SMP */
> if (p->prio < rq->curr->prio && cpu_online(cpu_of(rq)))
What happens to a always running CFS task which switches to RT? Luca
introduced a special migrate callback (next to push and pull)
specifically to deal with this scenario. A lot of new infrastructure for
this one use case, but still, do we care for it in RT as well?
https://lore.kernel.org/r/20190506044836.2914-4-luca.abeni@santannapisa.it
next prev parent reply other threads:[~2019-10-30 11:57 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 10:46 Qais Yousef
2019-10-23 12:34 ` Qais Yousef
2019-10-28 14:37 ` Peter Zijlstra
2019-10-28 18:01 ` Steven Rostedt
2019-10-28 20:50 ` Peter Zijlstra
2019-12-20 16:01 ` Qais Yousef
2019-12-20 17:18 ` Peter Zijlstra
2019-12-20 17:36 ` Qais Yousef
2019-11-07 9:15 ` Qais Yousef
2019-11-18 15:43 ` Qais Yousef
2019-11-18 15:53 ` Steven Rostedt
2019-11-18 16:12 ` Qais Yousef
2019-10-29 8:13 ` Vincent Guittot
2019-10-29 11:02 ` Qais Yousef
2019-10-29 11:17 ` Vincent Guittot
2019-10-29 11:48 ` Qais Yousef
2019-10-29 12:20 ` Vincent Guittot
2019-10-29 12:46 ` Qais Yousef
2019-10-29 12:54 ` Vincent Guittot
2019-10-29 13:02 ` Peter Zijlstra
2019-10-29 20:36 ` Patrick Bellasi
2019-10-30 8:04 ` Vincent Guittot
2019-10-30 9:26 ` Qais Yousef
2019-10-30 12:11 ` Quentin Perret
2019-10-30 11:57 ` Dietmar Eggemann [this message]
2019-10-30 17:43 ` Qais Yousef
2019-11-28 13:59 ` Dietmar Eggemann
2019-11-25 21:36 ` Steven Rostedt
2019-11-26 9:39 ` Qais Yousef
2019-12-25 10:38 ` [tip: sched/core] sched/rt: Make RT capacity-aware tip-bot2 for Qais Yousef
2020-01-31 10:06 ` [PATCH v2] sched: rt: Make RT capacity aware Pavan Kondeti
2020-01-31 15:34 ` Qais Yousef
[not found] ` <CAEU1=PnYryM26F-tNAT0JVUoFcygRgE374JiBeJPQeTEoZpANg@mail.gmail.com>
2020-02-03 5:32 ` Pavan Kondeti
2020-02-03 14:57 ` Qais Yousef
2020-02-03 14:27 ` Qais Yousef
2020-02-03 16:14 ` Steven Rostedt
2020-02-03 17:15 ` Valentin Schneider
2020-02-03 17:17 ` Qais Yousef
2020-02-03 18:12 ` Steven Rostedt
2020-02-03 19:03 ` Qais Yousef
2020-02-04 17:23 ` Dietmar Eggemann
2020-02-05 14:48 ` Qais Yousef
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=39c08971-5d07-8018-915b-9c6284f89d5d@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=bsegall@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.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
all inboxes | Powered by JetHome®