Messages in this thread | | | Subject | Re: [PATCH 05/16] sched: SCHED_DEADLINE policy implementation. | From | Steven Rostedt <> | Date | Tue, 10 Apr 2012 23:06:28 -0400 |
| |
On Fri, 2012-04-06 at 09:14 +0200, Juri Lelli wrote:
> +/* > + * Pure Earliest Deadline First (EDF) scheduling does not deal with the > + * possibility of a entity lasting more than what it declared, and thus > + * exhausting its runtime. > + * > + * Here we are interested in making runtime overrun possible, but we do > + * not want a entity which is misbehaving to affect the scheduling of all > + * other entities. > + * Therefore, a budgeting strategy called Constant Bandwidth Server (CBS) > + * is used, in order to confine each entity within its own bandwidth. > + * > + * This function deals exactly with that, and ensures that when the runtime > + * of a entity is replenished, its deadline is also postponed. That ensures > + * the overrunning entity can't interfere with other entity in the system and > + * can't make them miss their deadlines. Reasons why this kind of overruns > + * could happen are, typically, a entity voluntarily trying to overcume its
s/overcume/overcome/
-- Steve
> + * runtime, or it just underestimated it during sched_setscheduler_ex(). > + */ > +static void replenish_dl_entity(struct sched_dl_entity *dl_se) > +{ > +
| |