> > my original feature request (which was solved for us by Ingo's SCHED_IDLE)
> > was to run background jobs (esp. `rc5' that time) which shall _not_
> > (or only very minimally) compete with other running tasks, even with
> > nive-19 tasks (because we're using NQS/LSF style batch jobs which are
>
> Why can't you run those tasks at nice 18?
because nice-18 and nice-19 jobs will compete significantly:
PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
24713 root 20 18 184 184 132 R N 0 55.0 0.5 0:31 idle
24714 root 20 19 184 184 132 R N 0 28.9 0.5 0:16 idle
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
Harald
--
All SCSI disks will from now on ___ _____
be required to send an email notice 0--,| /OOOOOOO\
24 hours prior to complete hardware failure! <_/ / /OOOOOOOOOOO\
\ \/OOOOOOOOOOOOOOO\
\ OOOOOOOOOOOOOOOOO|//
Harald Koenig, \/\/\/\/\/\/\/\/\/
Inst.f.Theoret.Astrophysik // / \\ \
koenig@tat.physik.uni-tuebingen.de ^^^^^ ^^^^^
-
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/