mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolas Bonnefon <nicolas.bonnefon@fr.thalesgroup.com>
To: "Eldor Rødseth" <Eldor.Rodseth@eto.ericsson.se>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: SCHED_FIFO and SCHED_RR in 2.4.7-10custom kernel
Date: Fri, 26 Apr 2002 14:52:24 +0200	[thread overview]
Message-ID: <3CC58155000078A8@bgxplex3.bgx.airsys.thomson-csf.com> (raw)
In-Reply-To: <F9CC1B4C20A0D411A99E00508BDFA6A203D8AB00@enoasnt101.eto.ericsson.se>


> My application uses the possibility to change scheduling mechanism. When
> changing from SCHED_OTHER to SCHED_FIFO or SCHED_RR, my application causes
> the whole Linux PC to "hang". Prior to launching my own application, I
> launch a "superbash" application with higher priority than my own
> application. But I am not able to switch to the window where this
> "superbash" application is running to kill my own application. The PC
> simply does not respond to any input from the keyboard.

Have you tried without running X ?
A SCHED_FIFO or SCHED_RR task has ALWAYS priority over any SCHED_OTHER
task, so if your application sits in an infinite loop without blocking, the 
window manager cannot preempt it and you simply cannot switch x-term.
I think you should carefully debug your app in SCHED_OTHER mode first, and 
then switch to some real-time policy.

>
> I have used this mechanism before, and I am quite confident that this
> worked under kernel 2.4.2. Are you aware of anything that could explain
> this behaviour?

It would be surprising, but if you were sure of that, it would deserve some 
deeper investigations !

Regards
-- 
Nicolas Bonnefon
Radar Development/Digital Processing Engineer
Thales Air Defence - 7-9 rue des Mathurins
92223 Bagneux - France

  reply	other threads:[~2002-04-26 12:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 12:01 Eldor Rødseth (ETO)
2002-04-26 12:52 ` Nicolas Bonnefon [this message]
2002-04-26 16:25   ` george anzinger
2002-04-26 20:11   ` george anzinger

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=3CC58155000078A8@bgxplex3.bgx.airsys.thomson-csf.com \
    --to=nicolas.bonnefon@fr.thalesgroup.com \
    --cc=Eldor.Rodseth@eto.ericsson.se \
    --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

all inboxes | Powered by JetHome®