Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261338AbVAaUQL (ORCPT ); Mon, 31 Jan 2005 15:16:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261344AbVAaUQL (ORCPT ); Mon, 31 Jan 2005 15:16:11 -0500 Received: from mail26.syd.optusnet.com.au ([211.29.133.167]:63673 "EHLO mail26.syd.optusnet.com.au") by vger.kernel.org with ESMTP id S261338AbVAaUQE (ORCPT ); Mon, 31 Jan 2005 15:16:04 -0500 Message-ID: <41FE91D2.4000903@kolivas.org> Date: Tue, 01 Feb 2005 07:15:14 +1100 From: Con Kolivas User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Jack O'Quin" Cc: linux kernel , Andrew Morton , Ingo Molnar , Alexander Nyberg , Zwane Mwaikambo Subject: Re: [PATCH] sched - Implement priority and fifo support for SCHED_ISO References: <41F76746.5050801@kolivas.org> <87acqpjuoy.fsf@sulphur.joq.us> In-Reply-To: <87acqpjuoy.fsf@sulphur.joq.us> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigEA8B3FDDC8E00059CD551DB0" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3102 Lines: 74 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigEA8B3FDDC8E00059CD551DB0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Jack O'Quin wrote: > Con Kolivas 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 They're SCHED_ISO_FIFO which schedtool doesn't know about. > 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? Shouldn't matter. There must still be something wrong with my code... sigh. I'll look into it at some stage, but there doesn't seem much point. Cheers, Con --------------enigEA8B3FDDC8E00059CD551DB0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB/pHSZUg7+tp6mRURAtx0AJ944tz2PLtSwYYCHgzX6KtHje4jJQCfUQxT JNrJ2/py6rR3h9eaDONp780= =VIev -----END PGP SIGNATURE----- --------------enigEA8B3FDDC8E00059CD551DB0-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/