From: Steven Dake <sdake@mvista.com>
To: linux-kernel@vger.kernel.org
Subject: Re: interesting problem with priorities and /sbin/hotplug
Date: Wed, 09 Jul 2003 11:44:24 -0700 [thread overview]
Message-ID: <3F0C6288.4030502@mvista.com> (raw)
In-Reply-To: <20030709183435.GA17969@kroah.com>
Greg KH wrote:
>On Wed, Jul 09, 2003 at 11:26:05AM -0700, Steven Dake wrote:
>
>
>>Greg,
>>
>>We found a small problem with the scheduler with our Linux 2.4 O1
>>backport in that a certain kernel process, keventd, would create a
>>priority inversion. If a process was run at realtime priority level 99,
>>keventd would never run. The keventd process is required for the
>>console, creating the appearance that the system had stopped responding.
>>
>>This problem started me thinking about priority inversions with
>>/sbin/hotplug. I wanted to get your thoughts about priority inversion
>>impact on /sbin/hotplug. Should /sbin/hotplug run at priority level 99
>>realtime?
>>
>>
>
>I don't know, why would that help anything out? How would there be a
>priority inversion in the existing code?
>
>
I'm not sure if there is a problem, but one example to consider is the
following:
If a process is running with realtime priority 99 totally consuming the
system, and an /sbin/hotplug process is started by the kernel because of
a device insert or remove, /sbin/hotplug will never be scheduled if it
runs with standard priority. If that service depends on those hotplug
events, it will never see them (even though they have occured). Since
I'm no scheduler expert, I don't know if this is actually how the system
would behave.... I do know that it would be desireable to have
/sbin/hotplug always run even if other processes in the system are
running in realtime priority....
parent reply other threads:[~2003-07-09 18:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20030709183435.GA17969@kroah.com>]
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=3F0C6288.4030502@mvista.com \
--to=sdake@mvista.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox