mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "g-j v dijk" <aka_mr_zapper@hotmail.com>
To: roger.larsson@norran.net, linux-kernel@vger.kernel.org
Subject: Re: Problem with SCHED_RR and kernel 2.4.18-4GB
Date: Tue, 30 Dec 2003 10:42:48 +0100	[thread overview]
Message-ID: <BAY2-F70OY1YT5D6pm8000352f2@hotmail.com> (raw)

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

Yep, I checked all threads. Not all threads have sleeps, but they do use 
semaphores or some blocking OS calls. Are you saying that's not enough? I 
think it should be, else the threads have design flaws.

>[BTW you are not running the same code in both cases due to ifdefs...]

Yep, IMHO you don't have to set the schedule type in "OTHER" mode.

>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 like that Idea, it would be really appreciated if you could give me some 
sample code, just to get me started.

Thanks a lot,

Gert-Jan

_________________________________________________________________
MSN Search, for accurate results! http://search.msn.nl


             reply	other threads:[~2003-12-30  9:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-30  9:42 g-j v dijk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-29 23:47 Roger Larsson
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=BAY2-F70OY1YT5D6pm8000352f2@hotmail.com \
    --to=aka_mr_zapper@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roger.larsson@norran.net \
    /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®