OK I3 also works fine with respect to my nice test. One thing I do note
and I am not too sure how it might be fixed, is what happens when starting
what will be interactive programs.
Watching with top 's 0.3' I can see them lose priority in the 3-10 seconds it
takes them to setup. This is not that critical if they are the only thing trying
to run. If you have another (not niced) task eating cpu (like a kernel compile)
then intactive startup time suffers. Startup time is wait time that _is_ noticed
by users.
Is there some way we could tell the scheduler or the scheduler could learn that
a given _program_ is usually interactive so it should wait at bit (10 seconds on my
box would work) before starting to increase its priority numbers?
TIA
Ed Tomlinson
-
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/