From: Steven Rostedt <rostedt@goodmis.org>
To: Qais Yousef <qais.yousef@arm.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
bsegall@google.com, mgorman@suse.de,
linux-kernel@vger.kernel.org, parth@linux.ibm.com,
chris.hyser@oracle.com, pkondeti@codeaurora.org,
Valentin.Schneider@arm.com, patrick.bellasi@matbug.net,
David.Laight@aculab.com, pjt@google.com, pavel@ucw.cz,
tj@kernel.org, qperret@google.com, tim.c.chen@linux.intel.com,
Wei Wang <wvw@google.com>
Subject: Re: [PATCH 0/6] Add latency_nice priority
Date: Sat, 9 Apr 2022 13:28:29 -0400 [thread overview]
Message-ID: <20220409132829.16b03d69@rorschach.local.home> (raw)
In-Reply-To: <20220409170841.upcimeak2ch3aj35@wubuntu>
On Sat, 9 Apr 2022 18:08:41 +0100
Qais Yousef <qais.yousef@arm.com> wrote:
> One other corner case to consider if you're working on next version is what
> should happen when there are multiple tasks of the same priority on the rq. RT
> scheduler will push/pull tasks to ensure the task will get to run ASAP if
> there's another cpu at lower priority is available. Seems a lot of complexity
> to add to CFS, but at the same time if 2 important tasks require low latency
> are on the same rq, one of them will suffer without introducing the ability to
> migrate one of them where it can get to run sooner.
Instead of having the greedy algorithm of the RT push/pull logic, how
hard would it be to have the load balancer know of these tasks, and try
to keep them on different CPUs? When two are queued on the same CPU,
could it be possible to just trigger load balancing and let it do the
work?
-- Steve
next prev parent reply other threads:[~2022-04-09 17:28 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 16:14 [PATCH 0/6] Add latency_nice priority Vincent Guittot
2022-03-11 16:14 ` [PATCH 1/6] sched: Introduce latency-nice as a per-task attribute Vincent Guittot
2022-03-11 16:14 ` [PATCH 2/6] sched/core: Propagate parent task's latency requirements to the child task Vincent Guittot
2022-03-22 0:22 ` Tim Chen
2022-03-22 14:57 ` Vincent Guittot
2022-03-11 16:14 ` [PATCH 3/6] sched: Allow sched_{get,set}attr to change latency_nice of the task Vincent Guittot
2022-03-22 0:22 ` Tim Chen
2022-03-22 14:55 ` Vincent Guittot
2022-03-28 9:23 ` Dietmar Eggemann
2022-03-28 12:41 ` Vincent Guittot
2022-03-11 16:14 ` [PATCH 4/6] sched/core: Add permission checks for setting the latency_nice value Vincent Guittot
2022-03-11 16:14 ` [RFC 5/6] sched/fair: Take into account latency nice at wakeup Vincent Guittot
2022-03-15 0:53 ` Josh Don
2022-03-15 13:54 ` Vincent Guittot
2022-03-28 9:24 ` Dietmar Eggemann
2022-03-28 12:51 ` Vincent Guittot
2022-05-01 15:58 ` Tao Zhou
2022-05-02 9:54 ` Vincent Guittot
2022-05-02 12:30 ` Vincent Guittot
2022-05-02 15:08 ` Tao Zhou
2022-05-02 15:26 ` Tao Zhou
2022-05-02 15:47 ` Tao Zhou
2022-05-02 16:21 ` Vincent Guittot
2022-05-02 23:09 ` Tao Zhou
2022-05-03 2:30 ` Tao Zhou
2022-05-03 12:40 ` Vincent Guittot
2022-05-04 11:14 ` Chen Yu
2022-05-04 12:39 ` Vincent Guittot
2022-03-11 16:14 ` [RFC 6/6] sched/fair: Add sched group latency support Vincent Guittot
2022-03-15 0:58 ` Josh Don
2022-03-15 17:07 ` Vincent Guittot
2022-03-21 17:24 ` Tejun Heo
2022-03-22 16:10 ` Vincent Guittot
2022-03-22 16:40 ` Tejun Heo
2022-03-23 15:04 ` Vincent Guittot
2022-03-23 18:20 ` Chris Hyser
2022-03-22 16:41 ` Tim Chen
2022-03-23 15:23 ` Vincent Guittot
2022-03-22 16:39 ` [PATCH 0/6] Add latency_nice priority Qais Yousef
2022-03-23 15:32 ` Vincent Guittot
2022-03-24 17:25 ` Qais Yousef
2022-03-25 13:27 ` Vincent Guittot
2022-03-28 16:27 ` Qais Yousef
2022-03-30 7:30 ` Vincent Guittot
2022-03-28 9:24 ` Dietmar Eggemann
2022-03-28 12:56 ` Vincent Guittot
2022-04-01 12:15 ` Qais Yousef
2022-04-02 8:46 ` Vincent Guittot
2022-04-09 17:08 ` Qais Yousef
2022-04-09 17:28 ` Steven Rostedt [this message]
2022-04-09 18:10 ` Qais Yousef
2022-04-11 7:26 ` Vincent Guittot
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=20220409132829.16b03d69@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=David.Laight@aculab.com \
--cc=Valentin.Schneider@arm.com \
--cc=bsegall@google.com \
--cc=chris.hyser@oracle.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=parth@linux.ibm.com \
--cc=patrick.bellasi@matbug.net \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=pkondeti@codeaurora.org \
--cc=qais.yousef@arm.com \
--cc=qperret@google.com \
--cc=tim.c.chen@linux.intel.com \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=wvw@google.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