[lkml]   [2003]   [Mar]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] limits on SCHED_FIFO tasks
george anzinger <> wrote:
> If the issue is regaining control after some RT task goes into a loop,
> the way this is usually done is to keep a session around with a higher
> priority. Using this concept, one might provide tools that, from
> userland, insure that such a session exists prior to launching the
> "suspect" code. I fail to see the need for this sort of code in the
> kernel.

That works, until your shell calls ext3_mark_inode_dirty(), which blocks on
kjournald activity. kjournald is SCHED_OTHER, and never runs...

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:34    [W:4.275 / U:0.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site