Message-ID: <426535D8.5020406@nortel.com>
Date: Tue, 19 Apr 2005 10:46:16 -0600
From: Chris Friesen <cfriesen@nortel.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040115
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: question on 2.4 scheduler, threads, and priority inversion
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 912
Lines: 23

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 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/