Messages in this thread | | | From | yodaiken@chelm ... | Subject | Re: Schedule idle | Date | Tue, 10 Nov 1998 19:28:39 -0700 (MST) |
| |
> backround jobs like rc5 _shall_not_ steal 30% cpu time from real important > computation batch jobs but should only run when the system really is _idle_ > otherwise. even nice-10 vs. nice-19 isnt' decoupled enough: > > PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND > 24819 root 17 10 184 184 132 R N 0 84.1 0.5 0:50 idle > 24820 root 20 19 184 184 132 R N 0 8.8 0.5 0:05 idle
Decoupled enough for what? If you want RC5 jobs to not even use this tiny amount of cpu while the batch jobs are running, why not
start batch_job signal rc5 process to shut down if( !fork()) exec batch job else wait() restart rc5
Making the kernel do what can be done better by a shell script is not good.
- 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/
| |