From: Juri Lelli <juri.lelli@redhat.com>
To: Daniel Bristot de Oliveira <bristot@kernel.org>
Cc: Joel Fernandes <joel@joelfernandes.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
linux-kernel@vger.kernel.org,
Luca Abeni <luca.abeni@santannapisa.it>,
Tommaso Cucinotta <tommaso.cucinotta@santannapisa.it>,
Thomas Gleixner <tglx@linutronix.de>,
Vineeth Pillai <vineeth@bitbyteword.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [RFC PATCH V3 6/6] sched/fair: Implement starvation monitor
Date: Wed, 14 Jun 2023 16:15:12 +0200 [thread overview]
Message-ID: <ZInLcNqGpLCw8xsn@localhost.localdomain> (raw)
In-Reply-To: <4849295d-9aef-836f-0e5f-063e2075380a@kernel.org>
Hey,
So Daniel provided the gory details :) .. but please let me highlight
one of his points below, which I think it might clarify why we might
want to start with a special case, patch 6 improved approach, before
possibly moving to more complex implementations.
On 14/06/23 15:45, Daniel Bristot de Oliveira wrote:
...
> By postponing the enqueue/replanishment of the DL server here, we are fixing the
> problem in a practical way, that works without breaking existing useful properties &
> use-cases.
In my understanding, if we simply postpone actual activation of the DL
server up to the point it really needs to boost/run for giving CFS tasks
some breath (the infamous 0-laxity :), we save RT tasks from useless
interruptions and still can keep EDF/CBS working w/o much changes.
It looks like a low hanging fruit, small improvement on what we have today
than doesn't prevent us for implementing more complex features (i.e., full
blown hierarchical scheduling, alternative schedulers) in the future if
the need arises.
Thanks!
Juri
next prev parent reply other threads:[~2023-06-14 14:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 15:58 [RFC PATCH V3 0/6] SCHED_DEADLINE server infrastructure Daniel Bristot de Oliveira
2023-06-08 15:58 ` [RFC PATCH V3 1/6] sched: Unify runtime accounting across classes Daniel Bristot de Oliveira
2023-06-13 13:24 ` Phil Auld
2023-06-16 14:30 ` Valentin Schneider
2023-06-08 15:58 ` [RFC PATCH V3 2/6] sched/deadline: Collect sched_dl_entity initialization Daniel Bristot de Oliveira
2023-06-13 13:25 ` Phil Auld
2023-06-16 14:31 ` Valentin Schneider
2023-06-08 15:58 ` [RFC PATCH V3 3/6] sched/deadline: Move bandwidth accounting into {en,de}queue_dl_entity Daniel Bristot de Oliveira
2023-06-16 14:31 ` Valentin Schneider
2023-06-08 15:58 ` [RFC PATCH V3 4/6] sched/deadline: Introduce deadline servers Daniel Bristot de Oliveira
2023-06-13 13:21 ` Phil Auld
2023-06-23 16:47 ` Valentin Schneider
2023-07-04 15:52 ` Daniel Bristot de Oliveira
2023-07-04 17:25 ` Joel Fernandes
2023-07-04 17:28 ` Joel Fernandes
2023-06-08 15:58 ` [RFC PATCH V3 5/6] sched/fair: Add trivial fair server Daniel Bristot de Oliveira
2023-06-16 12:59 ` Peter Zijlstra
2023-06-16 13:00 ` Daniel Bristot de Oliveira
2023-06-16 13:12 ` Peter Zijlstra
2023-06-16 13:18 ` Daniel Bristot de Oliveira
2023-06-08 15:58 ` [RFC PATCH V3 6/6] sched/fair: Implement starvation monitor Daniel Bristot de Oliveira
2023-06-12 1:57 ` Joel Fernandes
2023-06-12 14:45 ` Daniel Bristot de Oliveira
2023-06-12 20:35 ` Joel Fernandes
2023-06-13 13:41 ` Daniel Bristot de Oliveira
2023-06-13 15:32 ` Joel Fernandes
2023-06-14 13:45 ` Daniel Bristot de Oliveira
2023-06-14 14:15 ` Juri Lelli [this message]
2023-06-14 18:27 ` Joel Fernandes
2023-06-14 18:24 ` Joel Fernandes
2023-06-16 12:05 ` Peter Zijlstra
2023-06-16 12:48 ` Daniel Bristot de Oliveira
2023-06-19 12:02 ` Peter Zijlstra
2023-06-19 14:58 ` Daniel Bristot de Oliveira
2023-06-16 11:56 ` Peter Zijlstra
2023-06-16 11:51 ` Peter Zijlstra
2023-06-16 13:27 ` Daniel Bristot de Oliveira
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=ZInLcNqGpLCw8xsn@localhost.localdomain \
--to=juri.lelli@redhat.com \
--cc=bristot@kernel.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@santannapisa.it \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
--cc=tglx@linutronix.de \
--cc=tommaso.cucinotta@santannapisa.it \
--cc=vincent.guittot@linaro.org \
--cc=vineeth@bitbyteword.org \
--cc=vschneid@redhat.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