That is a good and valid point
>
> 100 screen updates per second doesn't mean it is important if it only
> is twiddling of a baton or some progress bar. People simply stick such
> things in an outer loop - and that worked out to a update or two
> per second in 1989. Same code on todays machines results in hundreds
> of updates per second. Are we going to fix apps as our pcs becomes faster?
nice my_old_compute_intensive_app
We agree that only CPU intensive apps will cause the problem right?
So if we keep the CPU boosting mechanism, but only boost non-niced
processes (makes good sense in my twisted mind at least), we provide the
interactiveness benefits for the general case, and provide an easy way
to run unmaintained (or "semi broken" or whatever we will call them)
applications.
We end up "forcing" the user to nice some (hopefully few) CPU intensive
applications that didn't need nicing before. I can see that that will
be a problem.
But will it be a bigger problem than not having the interactiveness
boost at all?
Cheers,
-- ................................................................ : jakob@unthought.net : And I see the elder races, : :.........................: putrid forms of man : : Jakob Østergaard : See him rise and claim the earth, : : OZ9ABN : his downfall is at hand. : :.........................:............{Konkhra}...............: - 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/