question on 2.4 scheduler, threads, and priority inversion

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I seem to be having an issue with 2.4 and linuxthreads.

I have a program that spawns a child thread, and that child boosts itself into a realtime scheduler class.

The child then went crazy and turned into a cpu hog. At this point, a higher-priority task detected the hog, and tried to kill the process by sending a "kill -9" to the main thread. Unfortunately, it appears that there is some kind of priority-inversion thing happening, as the process did not die.

Is this expected behaviour? Is there any way around this? Do I need to put the main thread at a higher priority than any of the child threads? What about the manager thread?

Thanks,

Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux