From: Robert Love <rml@tech9.net>
To: george anzinger <george@mvista.com>
Cc: Andi Kleen <ak@muc.de>, Ian Collinson <icollinson@imerge.co.uk>,
"'Andrew Morton'" <akpm@zip.com.au>,
Mike Kravetz <kravetz@us.ibm.com>,
linux-kernel@vger.kernel.org, andrea@suse.de
Subject: Re: realtime scheduling problems with 2.4 linux kernel >= 2.4.10
Date: 05 Jun 2002 11:13:43 -0700 [thread overview]
Message-ID: <1023300843.912.295.camel@sinai> (raw)
In-Reply-To: <3CFE52D8.1A36682F@mvista.com>
On Wed, 2002-06-05 at 11:05, george anzinger wrote:
> 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.)
Good point.
> 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
> around.
Due to kernel.org's policy that all content must be kernel-related (has
something to do with the domain name, I suspect) my scheduler tools are
not there. You can get them at
http://tech9.net/rml/
however :)
Robert Love
next prev parent reply other threads:[~2002-06-05 18:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 11:53 realtime scheduling problems with 2.4 linux kernel >= 2.4.10 Ian Collinson
2002-06-05 12:17 ` Andi Kleen
2002-06-05 18:05 ` george anzinger
2002-06-05 18:13 ` Robert Love [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-30 17:54 Ian Collinson
2002-05-31 18:28 ` Mike Kravetz
2002-05-31 19:41 ` Andrea Arcangeli
2002-06-01 17:05 ` Andi Kleen
2002-06-03 16:03 ` Mike Kravetz
2002-06-03 20:08 ` Andrew Morton
2002-06-03 20:13 ` Robert Love
2002-06-03 21:09 ` Andrew Morton
2002-06-03 21:07 ` Andrea Arcangeli
2002-06-03 20:12 ` Andi Kleen
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=1023300843.912.295.camel@sinai \
--to=rml@tech9.net \
--cc=ak@muc.de \
--cc=akpm@zip.com.au \
--cc=andrea@suse.de \
--cc=george@mvista.com \
--cc=icollinson@imerge.co.uk \
--cc=kravetz@us.ibm.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