> Spell out what "important RT" means precisely and you will be in a position
> to make your code work. If you want a completely preemptable kernel, you
> have your work cut out for you. God alone knows what it means for a
> high priority RT task to "use the FS".
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
far more important than rc5, but far less important than interactive work).
so it's not an "important RT" thing in my eyes, `only' an important nuance
of scheduling policy.
if there is another solution which will claim only some very few % of CPU-time
for those background/idle jobs (vs. nice-19 tasks) I'd be happy to use it...
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/