From: David Laight <David.Laight@ACULAB.COM>
To: 'Youssef Esmat' <youssefesmat@chromium.org>,
Vincent Guittot <vincent.guittot@linaro.org>
Cc: "mingo@redhat.com" <mingo@redhat.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"juri.lelli@redhat.com" <juri.lelli@redhat.com>,
"dietmar.eggemann@arm.com" <dietmar.eggemann@arm.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"bsegall@google.com" <bsegall@google.com>,
"mgorman@suse.de" <mgorman@suse.de>,
"bristot@redhat.com" <bristot@redhat.com>,
"vschneid@redhat.com" <vschneid@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"parth@linux.ibm.com" <parth@linux.ibm.com>,
"qais.yousef@arm.com" <qais.yousef@arm.com>,
"chris.hyser@oracle.com" <chris.hyser@oracle.com>,
"valentin.schneider@arm.com" <valentin.schneider@arm.com>,
"patrick.bellasi@matbug.net" <patrick.bellasi@matbug.net>,
"pjt@google.com" <pjt@google.com>, "pavel@ucw.cz" <pavel@ucw.cz>,
"tj@kernel.org" <tj@kernel.org>,
"qperret@google.com" <qperret@google.com>,
"tim.c.chen@linux.intel.com" <tim.c.chen@linux.intel.com>,
"joshdon@google.com" <joshdon@google.com>,
"timj@gnu.org" <timj@gnu.org>,
"joel@joelfernandes.org" <joel@joelfernandes.org>
Subject: RE: [PATCH v5 7/7] sched/fair: Add latency list
Date: Sat, 8 Oct 2022 21:14:54 +0000 [thread overview]
Message-ID: <39d4ea27cfce4b7d977605f37f6da6fb@AcuMS.aculab.com> (raw)
In-Reply-To: <CA+q576OoP6Ebax8aGM234JRf+WOJFEwChs25qB9M_rt7+r1wuA@mail.gmail.com>
...
> Have we considered an approach where the task that is marked as
> latency sensitive gets a boosted nice value when it sleeps and is
> either scaled down exponentially as it runs, or immediately reset to
> its default when it runs for one tick?
Or use the RT scheduler for anything that requires low latency.
Isn't that what it is for?
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-10-08 21:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 14:39 [PATCH v5 0/7] Add latency priority for CFS class Vincent Guittot
2022-09-25 14:39 ` [PATCH v5 1/7] sched: Introduce latency-nice as a per-task attribute Vincent Guittot
2022-09-25 14:39 ` [PATCH v5 2/7] sched/core: Propagate parent task's latency requirements to the child task Vincent Guittot
2022-09-25 14:39 ` [PATCH v5 3/7] sched: Allow sched_{get,set}attr to change latency_nice of the task Vincent Guittot
2022-10-12 15:07 ` K Prateek Nayak
2022-10-12 15:44 ` Vincent Guittot
2022-09-25 14:39 ` [PATCH v5 4/7] sched/fair: Take into account latency priority at wakeup Vincent Guittot
2022-10-22 15:08 ` Chen Yu
2022-10-24 22:36 ` Vincent Guittot
2022-09-25 14:39 ` [PATCH v5 5/7] sched/fair: Add sched group latency support Vincent Guittot
2022-10-12 14:22 ` Qais Yousef
2022-10-12 15:42 ` Vincent Guittot
2022-10-12 16:07 ` Qais Yousef
2022-09-25 14:39 ` [PATCH v5 6/7] sched/core: Support latency priority with sched core Vincent Guittot
2022-09-25 14:39 ` [PATCH v5 7/7] sched/fair: Add latency list Vincent Guittot
2022-10-08 1:04 ` Youssef Esmat
2022-10-08 21:14 ` David Laight [this message]
2022-10-08 21:59 ` Steven Rostedt
2022-10-11 17:10 ` Vincent Guittot
2022-10-11 23:54 ` Youssef Esmat
2022-10-12 15:21 ` Vincent Guittot
2022-10-13 17:19 ` Youssef Esmat
2022-10-14 15:22 ` Vincent Guittot
2022-10-19 16:53 ` Vincent Guittot
2022-10-20 15:20 ` Vincent Guittot
2022-10-26 10:44 ` Dietmar Eggemann
2022-10-26 13:55 ` Vincent Guittot
2022-10-12 14:53 ` [PATCH v5 0/7] Add latency priority for CFS class K Prateek Nayak
2022-10-13 15:24 ` Vincent Guittot
2022-10-17 6:47 ` K Prateek Nayak
2022-10-25 6:36 ` K Prateek Nayak
2022-10-27 16:34 ` 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=39d4ea27cfce4b7d977605f37f6da6fb@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=chris.hyser@oracle.com \
--cc=dietmar.eggemann@arm.com \
--cc=joel@joelfernandes.org \
--cc=joshdon@google.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=qais.yousef@arm.com \
--cc=qperret@google.com \
--cc=rostedt@goodmis.org \
--cc=tim.c.chen@linux.intel.com \
--cc=timj@gnu.org \
--cc=tj@kernel.org \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=youssefesmat@chromium.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;
as well as URLs for NNTP newsgroup(s).