From: "Jack O'Quin" <joq@io.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
Alexander Nyberg <alexn@dsv.su.se>,
Zwane Mwaikambo <zwane@linuxpower.ca>
Subject: Re: [PATCH] sched - Implement priority and fifo support for SCHED_ISO
Date: Mon, 31 Jan 2005 12:54:21 -0600 [thread overview]
Message-ID: <87acqpjuoy.fsf@sulphur.joq.us> (raw)
In-Reply-To: <41F76746.5050801@kolivas.org> (Con Kolivas's message of "Wed, 26 Jan 2005 20:47:50 +1100")
Con Kolivas <kernel@kolivas.org> writes:
> While it is not clear what form the final soft real time
> implementation is, we should complete the partial implementation of
> SCHED_ISO that is in 2.6.11-rc2-mm1.
I finally had a chance to try this today. I applied a slightly
different patch (2.6.11-rc2-iso3.diff) on top of patch-2.6.11-rc2. I
tried to use 2.6.11-rc2-mm2, but could not due to conflicts with other
scheduler updates.
It is not clear whether the realtime threads are running in the new
scheduler class. Checking with schedtool yields odd results.
(Before, my old schedtool always said "POLICY I: SCHED_ISO".)
[joq@sulphur] jack_test/ $ pst jackd
2173 2173 TS - 0 19 0 0.0 SLs rt_sigsuspend jackd
2174 2174 ? 21 0 60 0 0.0 SL - jackd
2175 2175 TS - 0 23 0 0.0 SL rt_sigsuspend jackd
2176 2176 TS - 0 23 0 0.0 SL - jackd
2177 2177 ? 20 0 59 0 0.0 SL syscall_call jackd
2178 2178 ? 10 0 49 0 1.7 SL - jackd
[joq@sulphur] jack_test/ $ schedtool 2174 2176 2177 2178
PID 2174: PRIO 21, POLICY (null) , NICE 0
PID 2176: PRIO 0, POLICY N: SCHED_NORMAL, NICE 0
PID 2177: PRIO 20, POLICY (null) , NICE 0
PID 2178: PRIO 10, POLICY (null) , NICE 0
The results of the first run indicate something is badly wrong. It is
quite possible that I got confused and messed up the build somehow.
http://www.joq.us/jack/benchmarks/sched-iso3/jack_test3-2.6.11-rc2-q1-200501311225.log
http://www.joq.us/jack/benchmarks/sched-iso3/jack_test3-2.6.11-rc2-q1-200501311225.png
Loading the realtime-lsm and then running with SCHED_FIFO *does* work
as expected on this kernel. I should retry the test with *exactly*
the expected patch sequence. What would that be?
--
joq
next prev parent reply other threads:[~2005-01-31 18:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 9:47 Con Kolivas
2005-01-31 18:54 ` Jack O'Quin [this message]
2005-01-31 20:15 ` Con Kolivas
2005-01-31 20:30 ` Con Kolivas
2005-01-31 21:04 ` Jack O'Quin
2005-01-31 22:51 ` Jack O'Quin
2005-01-31 23:01 ` Con Kolivas
2005-02-01 2:27 ` Jack O'Quin
2005-02-01 2:46 ` Con Kolivas
2005-02-01 4:44 ` Jack O'Quin
2005-02-01 4:56 ` Con Kolivas
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=87acqpjuoy.fsf@sulphur.joq.us \
--to=joq@io.com \
--cc=akpm@osdl.org \
--cc=alexn@dsv.su.se \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zwane@linuxpower.ca \
/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®