From: Roger Larsson <roger.larsson@norran.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problem with SCHED_RR and kernel 2.4.18-4GB
Date: Tue, 30 Dec 2003 00:47:28 +0100 [thread overview]
Message-ID: <200312300047.28787.roger.larsson@norran.net> (raw)
> I'm a newbie at Linux, but have been busy developing (with some other
> people) sort of a DVB zapper demo application/stack on top of Hauppauge HW
> and SUSE 8.0 kernel 2.4.18-4GB for the last 2 months.
> As the stack wil eventually be ported to one (or more) dedicated HW
> platforms, we defined an OS independant API. Now, we want to be able to set
> priorities, and have sort of a realtime behaviour.
> The problem is that if I implement this, and set scheduling to be SCHED_RR,
> or SCHED_FIFO, my linux machine hangs. With SCHED_OTHER, I don't have that
> (note that for testing I used to set all prios to minimum (=1)).
The big difference is that if a tread running as SCHED_RR or SCHED_FIFO never
sleeps normal treads (like X, sh, login, ...) will not be given ANY CPU time
- computer will appear hanged.
[BTW you are not running the same code in both cases due to ifdefs...]
But it is possible to get out of this situation if you prepared for it
before... Use a higher priority monitor to detect looping RT processes and
reduce their priorities!
(I have code if you are interested, please CC me as I am not subscibed to
linux-kernel)
/RogerL
--
Roger Larsson
Skellefteå
Sweden
next reply other threads:[~2003-12-29 23:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 23:47 Roger Larsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-30 9:42 g-j v dijk
2003-12-29 11:08 g-j v dijk
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=200312300047.28787.roger.larsson@norran.net \
--to=roger.larsson@norran.net \
--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®