From: "'joe.korty@ccur.com'" <joe.korty@ccur.com>
To: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Cc: "'Andrew Morton'" <akpm@digeo.com>,
"'george anzinger'" <george@mvista.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'mingo@elte.hu'" <mingo@elte.hu>
Subject: Re: O(1) scheduler seems to lock up on sched_FIFO and sched_RR ta sks
Date: Thu, 19 Jun 2003 00:34:41 -0400 [thread overview]
Message-ID: <20030619043441.GA1304@rudolph.ccur.com> (raw)
In-Reply-To: <A46BBDB345A7D5118EC90002A5072C780DD16D38@orsmsx116.jf.intel.com>
On Wed, Jun 18, 2003 at 06:44:42PM -0700, Perez-Gonzalez, Inaky wrote:
>
> Now that we are at that, it might be wise to add a higher-than-anything
> priority that the kernel code can use (what would be 100 for user space,
> but off-limits), so even FIFO 99 code in user space cannot block out
> the migration thread, keventd and friends.
I would prefer users have the ability to put one or two truly critical RT
tasks above keventd & family. Such tasks would have to follow certain rules
.. run & sleep quick .. limited or no device IO .. most communication to
other tasks through shared memory .. possibly others.
There are those willing to follow whatever rules necessary & split up their
application into tasks any which way in order to get high responsiveness to a
critical but small part of their application. If you follow the rules, you
should be allowed to put a carefully crafted task above the system daemons
(with the possible exception of the migration daemon).
Joe
next prev parent reply other threads:[~2003-06-19 4:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 1:44 O(1) scheduler seems to lock up on sched_FIFO and sched_RR ta sks Perez-Gonzalez, Inaky
2003-06-19 1:58 ` Robert Love
2003-06-19 2:02 ` george anzinger
2003-06-19 4:34 ` 'joe.korty@ccur.com' [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-19 2:55 Perez-Gonzalez, Inaky
2003-06-19 4:38 Perez-Gonzalez, Inaky
2003-06-19 6:06 Perez-Gonzalez, Inaky
2003-06-19 6:07 ` Ingo Molnar
2003-06-19 16:00 ` george anzinger
2003-06-19 17:19 ` 'joe.korty@ccur.com'
2003-06-19 17:23 ` Robert Love
2003-06-19 17:28 ` Joe Korty
2003-06-19 6:52 Perez-Gonzalez, Inaky
2003-06-19 17:43 ` Robert Love
2003-06-19 18:31 Perez-Gonzalez, Inaky
2003-06-19 18:36 ` Robert Love
2003-06-19 19:22 Perez-Gonzalez, Inaky
2003-06-20 2:53 Perez-Gonzalez, Inaky
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=20030619043441.GA1304@rudolph.ccur.com \
--to=joe.korty@ccur.com \
--cc=akpm@digeo.com \
--cc=george@mvista.com \
--cc=inaky.perez-gonzalez@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.