Re: [RFC 2/5] sched: Add CPU rate soft caps
- From: "Balbir Singh" <balbir@xxxxxxxxxx>
- Date: Sun, 28 May 2006 13:08:16 +0530
On 5/28/06, Peter Williams <pwil3058@xxxxxxxxxxxxxx> wrote:
Peter Williams wrote:
> Balbir Singh wrote:
>> On 5/26/06, Peter Williams <pwil3058@xxxxxxxxxxxxxx> wrote:
>> <snip>
>>>
>>> Notes:
>>>
>>> 1. To minimize the overhead incurred when testing to skip caps
>>> processing for
>>> uncapped tasks a new flag PF_HAS_CAP has been added to flags.
>>>
>>> 2. The implementation involves the addition of two priority slots to the
>>> run queue priority arrays and this means that MAX_PRIO no longer
>>> represents the scheduling priority of the idle process and can't be
>>> used to
>>> test whether priority values are in the valid range. To alleviate this
>>> problem a new function sched_idle_prio() has been provided.
>>
>> I am a little confused by this. Why link the bandwidth expired tasks a
>> cpu (its caps) to a priority slot? Is this a hack to conitnue using
>> the prio_array? why not move such tasks to the expired array?
>
> Because it won't work as after the array switch they may get to run
> before tasks who aren't exceeding their cap (or don't have a cap).
That behaviour would be fair. Let the priority govern who gets to run
first (irrespective of their cap) and then use the cap to limit their
timeslice (execution time).
Another important reason for using these slots is that it allows waking
tasks to preempt tasks that have exceeded their cap.
But among all tasks that exceed their cap (there is no priority based
scheduling). As far as preemption is concerned, if they are moved to
the expired array, capped tasks will only run if an array switch takes
place. If it does, then they get their fare share of the cap again
until they exceed their cap.
Balbir
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [RFC 2/5] sched: Add CPU rate soft caps
- From: Peter Williams
- Re: [RFC 2/5] sched: Add CPU rate soft caps
- References:
- [RFC 0/5] sched: Add CPU rate caps
- From: Peter Williams
- [RFC 2/5] sched: Add CPU rate soft caps
- From: Peter Williams
- Re: [RFC 2/5] sched: Add CPU rate soft caps
- From: Balbir Singh
- Re: [RFC 2/5] sched: Add CPU rate soft caps
- From: Peter Williams
- Re: [RFC 2/5] sched: Add CPU rate soft caps
- From: Peter Williams
- [RFC 0/5] sched: Add CPU rate caps
- Prev by Date: 2.6.16.x - relatively low volume and high noice using snd-ali15451
- Next by Date: Re: Linux and Wireless USB Adaptor
- Previous by thread: Re: [RFC 2/5] sched: Add CPU rate soft caps
- Next by thread: Re: [RFC 2/5] sched: Add CPU rate soft caps
- Index(es):
Relevant Pages
|
|