From 08d4eb452c7990be7e4537cfd39d9c276a768239 Mon Sep 17 00:00:00 2001 From: GeunSik Lim Date: Thu, 28 May 2009 10:36:14 +0900 Subject: [PATCH] --- yaml --- r: 145718 b: refs/heads/master c: f04d82b7e0c63d0251f9952a537a4bc4d73aa1a9 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/scheduler/sched-rt-group.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index bfe2d1acd44d..f6f05d62e827 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 294ae4011530d008c59c4fb9847738e39228821e +refs/heads/master: f04d82b7e0c63d0251f9952a537a4bc4d73aa1a9 diff --git a/trunk/Documentation/scheduler/sched-rt-group.txt b/trunk/Documentation/scheduler/sched-rt-group.txt index eb74b014a3f8..1df7f9cdab05 100644 --- a/trunk/Documentation/scheduler/sched-rt-group.txt +++ b/trunk/Documentation/scheduler/sched-rt-group.txt @@ -187,7 +187,7 @@ get their allocated time. Implementing SCHED_EDF might take a while to complete. Priority Inheritance is the biggest challenge as the current linux PI infrastructure is geared towards -the limited static priority levels 0-139. With deadline scheduling you need to +the limited static priority levels 0-99. With deadline scheduling you need to do deadline inheritance (since priority is inversely proportional to the deadline delta (deadline - now).