[lkml]   [2002]   [Jun]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: realtime scheduling problems with 2.4 linux kernel >= 2.4.10
Andi Kleen wrote:
> On Wed, Jun 05, 2002 at 01:53:06PM +0200, Ian Collinson wrote:
> >
> > Are there any potentially negative consequences of this fix, apart from
> > those already mentioned?
> I don't think so.
> It could still fail when you install a prio=99, SCHED_FIFO process.
> > I certainly vote for this feature being preserved, as it is extremely useful
> > for debugging realtime priority apps. FYI, we narrowed it down to breaking
> > in either 2.4.10-pre11 or pre12.
> That was when the low latency console changes went in. Before that console
> switches could interrupt scheduling for a long time, causing problems
> for other realtime people. The change was to move the expensive parts
> of the console switch to keventd.

So that means that, with the above change to prio 99, we
reintroduce the latency problem, only now it is in a task
(keventd) and not an interrupt? (I know, I know, the work
has to be done somewhere. At least this way we can control
what priority level it is done at. I.e. this is a step in
the right direction. I just what folks to be aware of the
latency issue and where it is.)

For what its worth, you can change the priority of keventd
AFTER a system is up. Robert Love's real time tools contain
a program (rt I think) that will do this for you. Just
follow the URL for preemption in my sig. file and look

George Anzinger
Real time sched:
Preemption patch:
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:22    [W:0.050 / U:0.812 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site