On Fri, 2007-10-19 at 14:43 -0400, Steven Rostedt wrote:
> plain text document attachment (rt-balance-pull-tasks.patch)
> +static int pull_rt_task(struct rq *this_rq)
> +{
> + struct task_struct *next;
> + struct task_struct *p;
> + struct rq *src_rq;
> + int this_cpu = this_rq->cpu;
> + int cpu;
> + int ret = 0;
> +
> + assert_spin_locked(&this_rq->lock);
> +
> + if (likely(!atomic_read(&rt_overload)))
> + return 0;
This seems to be the only usage of rt_overload. I'm not sure its worth
keeping it around for this.
> + next = pick_next_task_rt(this_rq);
> +
> + for_each_cpu_mask(cpu, rto_cpumask) {
> + if (this_cpu == cpu)
> + continue;
...
> + }
> +
> + return ret;
> +}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
