[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200908222252.GC1005@bug>
Date: Wed, 9 Sep 2020 00:22:52 +0200
From: Pavel Machek <pavel@....cz>
To: Juri Lelli <juri.lelli@...hat.com>
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!
> 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 is not white box with CPU inside, it is not even an userland process, afaict.
Subject is quite confusing.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Powered by blists - more mailing lists