Home
last modified time | relevance | path

Searched refs:leftmost (Results 1 – 7 of 7) sorted by relevance

/linux-4.4.14/kernel/locking/
Drtmutex.c185 int leftmost = 1; in rt_mutex_enqueue() local
194 leftmost = 0; in rt_mutex_enqueue()
198 if (leftmost) in rt_mutex_enqueue()
224 int leftmost = 1; in rt_mutex_enqueue_pi() local
233 leftmost = 0; in rt_mutex_enqueue_pi()
237 if (leftmost) in rt_mutex_enqueue_pi()
/linux-4.4.14/kernel/sched/
Ddeadline.c163 int leftmost = 1; in enqueue_pushable_dl_task() local
175 leftmost = 0; in enqueue_pushable_dl_task()
179 if (leftmost) in enqueue_pushable_dl_task()
837 struct rb_node *leftmost = dl_rq->rb_leftmost; in dec_dl_deadline() local
840 entry = rb_entry(leftmost, struct sched_dl_entity, rb_node); in dec_dl_deadline()
888 int leftmost = 1; in __enqueue_dl_entity() local
899 leftmost = 0; in __enqueue_dl_entity()
903 if (leftmost) in __enqueue_dl_entity()
Dfair.c491 int leftmost = 1; in __enqueue_entity() local
507 leftmost = 0; in __enqueue_entity()
515 if (leftmost) in __enqueue_entity()
/linux-4.4.14/Documentation/scheduler/
Dsched-design-CFS.txt69 p->se.vruntime key. CFS picks the "leftmost" task from this tree and sticks to it.
72 to become the "leftmost task" and thus get on the CPU within a deterministic
79 becomes the "leftmost task" of the time-ordered rbtree it maintains (plus a
80 small amount of "granularity" distance relative to the leftmost task so that we
81 do not over-schedule tasks and trash the cache), then the new leftmost task is
/linux-4.4.14/kernel/time/
Dhrtimer.c986 int leftmost; in hrtimer_start_range_ns() local
1005 leftmost = enqueue_hrtimer(timer, new_base); in hrtimer_start_range_ns()
1006 if (!leftmost) in hrtimer_start_range_ns()
/linux-4.4.14/Documentation/
Drbtree.txt282 * Iterate to find the leftmost such node N.
294 return node; /* node is leftmost match */
/linux-4.4.14/Documentation/devicetree/
Dbooting-without-of.txt827 is 31. In the case of node names, this is only the leftmost part of