On Tuesday 29 July 2003 10:40, Timothy Miller wrote:
> IF it's possible to intelligently determine interactivity and other such
> things, and lots of impressive progress is being made in that area, then
> that is definately preferable.
But it's not possible to determine realtimeness automatically, as far as I
know.
> ...It might help to have an API for real-time processes that is accessible
> by non-root tasks. If a task sets itself to real-time, its scheduling
> is more predictable, but it gets a shorter timeslice (perhaps) so that
> being real-time doesn't adversely impact the system when abused.
That's precisely what Davide's SCHED_SOFTRR is and does.
> The nice thing about the smart schedulers is that (a) no one has to
> change their apps (although they can tweak to cooperate better), and (b)
> future apps will behave well without us having to anticipate anything.
On the other hand, you want to avoid messing up the kernel just because some
app is broken. While it's not always possible to avoid changing apps to fix
them, in the case of audio apps on Linux at this point in time, it most
certainly is.
Regards,
Daniel
-
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 Jul 31 2003 - 22:00:41 EST