All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortel.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: question on 2.4 scheduler, threads, and priority inversion
Date: Tue, 19 Apr 2005 17:38:27 -0600	[thread overview]
Message-ID: <42659673.9080901@nortel.com> (raw)
In-Reply-To: <426594B1.9000307@shaw.ca>

Robert Hancock wrote:

> I believe that in the old LinuxThreads implementation the manager thread 
>  is the one that handles all signals, so it may need its priority 
> increased as well. NPTL threads likely handle this much better (there is 
> no manager thread).

Some experimenting leads me to believe that both the main thread and the 
manager thread must be of higher priority than the cpu hogging thread, 
otherwise priority inversion issues occur.

I was fairly shocked that even a "kill -9" failed to work though...

Chris


  reply	other threads:[~2005-04-19 23:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3V45v-tx-39@gated-at.bofh.it>
2005-04-19 23:30 ` question on 2.4 scheduler, threads, and priority inversion Robert Hancock
2005-04-19 23:38   ` Chris Friesen [this message]
2005-04-19 16:46 Chris Friesen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42659673.9080901@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.