Actually, since task_pri is calculated from convert_prio() that check
should never be hit. But, I'm paranoid, and instead of dropping the
check, we can do the same as what cpupri_set() does. Which is to BUG.
-- Steve
>From aac271901d6ef5ad19c52f166bf130ad27515b5f Mon Sep 17 00:00:00 2001
From: "S
On Wed, 09 Apr 2014 05:50:10 +0200
Mike Galbraith wrote:
> Hi Steven,
>
> Seems c92211d9b7727 introduced a buglet.
>
> --snip--
>
> Bail on task_pri >= MAX_RT_PRIO excludes userspace prio 98 and 99 tasks,
> which map to 100 and 101 respectively.
>
> A user reported that given two SCHED_RR tas
Hi Steven,
Seems c92211d9b7727 introduced a buglet.
--snip--
Bail on task_pri >= MAX_RT_PRIO excludes userspace prio 98 and 99 tasks,
which map to 100 and 101 respectively.
A user reported that given two SCHED_RR tasks, one hog, one light, the light
task may be stacked on top of the hog iff pri
3 matches
Mail list logo