On Fri, 2007-10-12 at 12:29 +0200, Peter Zijlstra wrote:
> I'm wondering why we need the cpu prio management stuff.
I know we covered most of this on IRC, but let me recap so everyone can
follow the thread:
1) The cpupri alg is just one search alg vs the other. I think we are
all in agreement t
On Fri, 2007-10-12 at 07:47 -0400, Steven Rostedt wrote:
> --
>
> 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:
> >
> > c
--
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_
Hi Gregory,
On Thu, 2007-10-11 at 17:59 -0400, Gregory Haskins wrote:
> The current series applies to 23-rt1-pre1.
>
> This is a snapshot of the current work-in-progress for the rt-overload
> enhancements. The primary motivation for the series to to improve the
> algorithm for distributing RT ta
The current series applies to 23-rt1-pre1.
This is a snapshot of the current work-in-progress for the rt-overload
enhancements. The primary motivation for the series to to improve the
algorithm for distributing RT tasks to keep the highest tasks active. The
current system tends to blast IPIs "sh
5 matches
Mail list logo
