public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Korty <joe.korty@ccur.com>
To: george anzinger <george@mvista.com>
Cc: lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: O(1) scheduler seems to lock up on sched_FIFO and sched_RR tasks
Date: Wed, 18 Jun 2003 18:57:10 -0400	[thread overview]
Message-ID: <20030618225710.GA20631@tsunami.ccur.com> (raw)
In-Reply-To: <3EF0E7AC.60007@mvista.com>

> >Hi George,
> > When I boost the priority of each of the per-cpu 'events/%d' daemon to
> >96, the problem goes away.
> 
> Seems like your saying that the events workqueues are involved in the 
> scheduler in some ugly way.  Certainly not what your average rt 
> programmer would expect :(  What is going on here?


My guess is that tty/ptty driver character processing is done by the
event daemons.  In which case your high priority bash is running but the
characters it puts out (if any) cannot be seen nor are the characters
you type in passed to bash, until the mid-priority process exits and
lets the event daemon run.

I view this as a kind of priority inversion.  The only solution is for
RT users to learn what each daemon does and hand-boost the priority of
each to the RT priority appropriate to their mix of RT applications.

Joe

      parent reply	other threads:[~2003-06-18 22:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 16:47 O(1) scheduler seems to lock up on sched_FIFO and sched_RR tasks george anzinger
2003-06-18 19:34 ` Joe Korty
2003-06-18 22:29   ` george anzinger
2003-06-18 22:56     ` Andrew Morton
2003-06-18 22:57     ` Joe Korty [this message]

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=20030618225710.GA20631@tsunami.ccur.com \
    --to=joe.korty@ccur.com \
    --cc=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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