Skip to content
  • Gregory Haskins's avatar
    sched: use highest_prio.next to optimize pull operations · 74ab8e4f
    Gregory Haskins authored
    
    
    We currently take the rq->lock for every cpu in an overload state during
    pull_rt_tasks().  However, we now have enough information via the
    highest_prio.[curr|next] fields to determine if there is any tasks of
    interest to warrant the overhead of the rq->lock, before we actually take
    it.  So we use this information to reduce lock contention during the
    pull for the case where the source-rq doesnt have tasks that preempt
    the current task.
    
    Signed-off-by: default avatarGregory Haskins <ghaskins@novell.com>
    74ab8e4f