> It would be nice would be the ability to _limit_ the system load due
> to processes other than the one running in the foreground, so you
> can receive mail, updatedb runs, your local news spool expires etc.
> without significantly impacting the game you're playing or the film
> you're watching.
>
> What happens now is typically, you're playing away and unexpectedly,
> some routine system maintenance process runs ruining the interaction
> for a while. "Don't run anything else" isn't practical if you take
> it to mean "kill crond while playing games".
I'm working on it, every once in a while. Whenever a nice
idea crosses my mind, I start thinking very hard and every
once in a while I come up with something useful.
The scheduler patch I just put out has something useful,
which might help with interactive performance -- it was
just a side effect of something else I wanted to do, but
it helps.
I am thinking about how to improve it even more (and how
to cut the overhead down some more); as of yet, it's
completely suitable for normal use, but it shows a bit
higher overhead than the normal system. With some help
I could both remove the overhead (easy) and keep the
nice feature introduced by the overhead...
Rik.
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/