Messages in this thread | | | Date | Fri, 12 Oct 2007 07:47:15 -0400 (EDT) | From | Steven Rostedt <> | Subject | Re: [PATCH 0/7] RT: (RFC) RT-Overload/Sched enhancements |
| |
--
On Fri, 12 Oct 2007, Peter Zijlstra wrote:
> > And for that, steve's rq->curr_prio field seems quite suitable. > > so instead of the: > for (3 tries) > find lowest cpu > try push > > we do: > > cpu_hotplug_lock(); > cpus_and(mask, p->cpus_allowed, online_cpus); > for_each_cpu_mask(i, mask) { > if (cpu_rq(i)->curr_prio > p->prio && push_task(p, i)) > break; > } > cpu_hotplug_unlock();
The thing I'm worried about is that we pushed off a rt task that is higher in prio than another rt task on another cpu, and we'll cause a bunch of rt task bouncing. That is what I'm trying to avoid.
BTW, my logging has showed that I have yet to hit a 2cd try (but I admit, this is a very limited test set).
-- Steve - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |