On Sun, 2007-03-18 at 13:50 +0530, jimmy bahuleyan wrote:
> maybe if it is possible to classify program behaviors that cause RSDL to
> do bad (relatively) or the mainline scheduler to jitter, we could try
> modifying the existing heuristics to get a better default scheduler.
>
> of course, it wouldn't be able to cater to all the workloads and would
> meet everybody's definition of optimal. but getting close to optimal in
> most cases should be a good enough goal for linux's default sched!
>
> i've been following this thread, and there's been many instances of
> 'RSDL is gr8' and 'RSDL regresses'.
>
> maybe RSDL isn't the answer. maybe the current mainline sched isn't
> either. but RSDL definitely has done *something* right.
Agreed.
> What i think is needed is 'why this works here' and 'how to get this
> behavior to work with some other possibly conflicting but important
> workloads'.
>
> (just my 2c :-)
IMHO, that's worth more than 2c.
-Mike
-
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/
