On Tue, 26 Feb 2002, Christoph Hellwig wrote:
> They shouldn't, But many old drivers do (and _had to_):
>
> current->policy = SCHED_YIELD;
> schedule();
>
> which isn't possible with the new scheduler.
Let's see, the choices are to (a) keep the old scheduler which has many
performance issues, or (b) put in the new scheduler and let people who
need the old drivers either fix them or stop upgrading.
Bad performance should go the way of a.out kernels and xiafs (which at
least did have utility), not be justified as a way to force people to
patch their kernel.
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.- 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/
This archive was generated by hypermail 2b29 : Thu Feb 28 2002 - 21:00:45 EST