> Pardon the suggestion of a dumb hueristic, feel free to ignore me:
> would it work to run-first processes that have modified their iopl()
> level? i.e. "if you access hardware directly, we'll treat you specially
> in the scheduler"?
we did this in the Red Hat kernel, just as a quick hack to boost X without
having to modify X (bleh). While it worked very well in practice, it's a
really bad idea from an interface design POV, because it singles out X
mostly based on a random characteristics of X, but leaves out some other
tasks that are 'suffering' from not being recognized as interactive, but
still having a user watching them (and expecting keypresses to react
fast): games, xine, XMMS, etc.
> An alternative is to encourage distros to set some sort of flag for
> processes like the X server, when it is run. This sounds suspiciously
> like the existing "renice X server" hack, but it could be something like
> changing the X server from SCHED_OTHER to SCHED_HW_ACCESS instead.
yes, an ELF flag might work, or my suggestion to allow applications to
increase their priority (up until a certain degree).
Ingo
-
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/