lkml.org 
[lkml]   [2012]   [Apr]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 05/16] sched: SCHED_DEADLINE policy implementation.
    On 04/11/2012 05:06 AM, Steven Rostedt wrote:
    > 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)
    >> +{
    >> +
    >

    Thanks!

    - Juri


    \
     
     \ /
      Last update: 2012-04-11 08:57    [W:0.034 / U:0.292 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site