From: Juri Lelli <juri.lelli@redhat.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: peterz@infradead.org, mingo@redhat.com, rostedt@goodmis.org,
tglx@linutronix.de, linux-kernel@vger.kernel.org,
luca.abeni@santannapisa.it, tommaso.cucinotta@santannapisa.it,
alessio.balsini@gmail.com, bristot@redhat.com,
dietmar.eggemann@arm.com, linux-rt-users@vger.kernel.org,
mtosatti@redhat.com, williams@redhat.com,
valentin.schneider@arm.com
Subject: Re: [RFC PATCH v2 0/6] SCHED_DEADLINE server infrastructure
Date: Wed, 9 Sep 2020 07:51:03 +0200 [thread overview]
Message-ID: <20200909055103.GA18215@localhost.localdomain> (raw)
In-Reply-To: <20200908222252.GC1005@bug>
Hi Pavel,
On 09/09/20 00:22, Pavel Machek wrote:
> Hi!
>
> > This is RFC v2 of Peter's SCHED_DEADLINE server infrastructure
> > implementation [1].
> >
> > SCHED_DEADLINE servers can help fixing starvation issues of low priority tasks (e.g.,
> > SCHED_OTHER) when higher priority tasks monopolize CPU cycles. Today we have RT
> > Throttling; DEADLINE servers should be able to replace and improve that.
>
> It would be worth noting what "server" is in this context.
It comes from Constant Bandwidth Server (CBS), that SCHED_DEADLINE is
implementing [1].
>
> It is not white box with CPU inside, it is not even an userland process, afaict.
>
> Subject is quite confusing.
Best,
Juri
1 - https://elixir.bootlin.com/linux/latest/source/Documentation/scheduler/sched-deadline.rst#L42
prev parent reply other threads:[~2020-09-09 5:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 9:50 [RFC PATCH v2 0/6] SCHED_DEADLINE server infrastructure Juri Lelli
2020-08-07 9:50 ` [RFC PATCH v2 1/6] sched: Unify runtime accounting across classes Juri Lelli
2020-08-07 9:50 ` [RFC PATCH v2 2/6] sched/deadline: Collect sched_dl_entity initialization Juri Lelli
2020-08-07 9:50 ` [RFC PATCH v2 3/6] sched/deadline: Move bandwidth accounting into {en,de}queue_dl_entity Juri Lelli
2020-08-07 9:50 ` [RFC PATCH v2 4/6] sched/deadline: Introduce deadline servers Juri Lelli
2020-10-06 7:56 ` luca abeni
2020-10-06 9:35 ` Juri Lelli
2020-10-06 9:51 ` luca abeni
2020-08-07 9:50 ` [RFC PATCH v2 5/6] sched/fair: Add trivial fair server Juri Lelli
2020-08-07 9:56 ` [RFC PATCH v2 6/6] sched/fair: Implement starvation monitor Juri Lelli
2020-08-07 10:46 ` peterz
2020-08-07 11:30 ` Daniel Bristot de Oliveira
2020-08-07 12:50 ` Juri Lelli
2020-08-07 13:49 ` luca abeni
2020-08-07 14:11 ` peterz
2020-08-07 16:48 ` Daniel Bristot de Oliveira
2020-08-07 13:28 ` luca abeni
2020-08-07 13:43 ` Juri Lelli
2020-08-07 13:55 ` luca abeni
2020-08-07 14:11 ` Juri Lelli
2020-08-07 14:13 ` peterz
2020-08-07 15:06 ` Juri Lelli
2020-08-07 13:16 ` [RFC PATCH v2 0/6] SCHED_DEADLINE server infrastructure luca abeni
2020-08-07 13:30 ` Juri Lelli
2020-08-07 13:41 ` luca abeni
2020-08-07 14:04 ` Juri Lelli
2020-08-07 14:14 ` peterz
2020-09-08 22:22 ` Pavel Machek
2020-09-09 5:51 ` Juri Lelli [this message]
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=20200909055103.GA18215@localhost.localdomain \
--to=juri.lelli@redhat.com \
--cc=alessio.balsini@gmail.com \
--cc=bristot@redhat.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=luca.abeni@santannapisa.it \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tommaso.cucinotta@santannapisa.it \
--cc=valentin.schneider@arm.com \
--cc=williams@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;
as well as URLs for NNTP newsgroup(s).