[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 9 Sep 2020 07:51:03 +0200
From: Juri Lelli <juri.lelli@...hat.com>
To: Pavel Machek <pavel@....cz>
Cc: peterz@...radead.org, mingo@...hat.com, rostedt@...dmis.org,
tglx@...utronix.de, linux-kernel@...r.kernel.org,
luca.abeni@...tannapisa.it, tommaso.cucinotta@...tannapisa.it,
alessio.balsini@...il.com, bristot@...hat.com,
dietmar.eggemann@....com, linux-rt-users@...r.kernel.org,
mtosatti@...hat.com, williams@...hat.com,
valentin.schneider@....com
Subject: Re: [RFC PATCH v2 0/6] SCHED_DEADLINE server infrastructure
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
Powered by blists - more mailing lists