From: Andrew Morton <akpm@digeo.com>
To: george anzinger <george@mvista.com>
Cc: async@cc.gatech.edu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] limits on SCHED_FIFO tasks
Date: Tue, 18 Mar 2003 19:04:07 -0800 [thread overview]
Message-ID: <20030318190407.37a39db1.akpm@digeo.com> (raw)
In-Reply-To: <3E77C40D.4090700@mvista.com>
george anzinger <george@mvista.com> 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...
next prev parent reply other threads:[~2003-03-19 2:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 23:51 rm
2003-03-19 1:12 ` george anzinger
2003-03-19 2:38 ` rm
2003-03-19 3:04 ` Andrew Morton [this message]
2003-03-19 8:22 ` george anzinger
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=20030318190407.37a39db1.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=async@cc.gatech.edu \
--cc=george@mvista.com \
--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®