From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261263AbULHQ6g (ORCPT ); Wed, 8 Dec 2004 11:58:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261265AbULHQ6g (ORCPT ); Wed, 8 Dec 2004 11:58:36 -0500 Received: from viper.oldcity.dca.net ([216.158.38.4]:27577 "HELO viper.oldcity.dca.net") by vger.kernel.org with SMTP id S261263AbULHQ6V (ORCPT ); Wed, 8 Dec 2004 11:58:21 -0500 Subject: Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm3-V0.7.32-6 From: Lee Revell To: "K.R. Foley" Cc: Ingo Molnar , linux-kernel@vger.kernel.org, Rui Nuno Capela , Mark_H_Johnson@Raytheon.com, Bill Huey , Adam Heath , Florian Schmidt , Thomas Gleixner , Michal Schmidt , Fernando Pablo Lopez-Lezcano , Karsten Wiese , Gunther Persoons , emann@mrv.com, Shane Shrybman , Amit Shah , Esben Nielsen In-Reply-To: <41B7314E.1050904@cybsft.com> References: <20041117124234.GA25956@elte.hu> <20041118123521.GA29091@elte.hu> <20041118164612.GA17040@elte.hu> <20041122005411.GA19363@elte.hu> <20041123175823.GA8803@elte.hu> <20041124101626.GA31788@elte.hu> <20041203205807.GA25578@elte.hu> <20041207132927.GA4846@elte.hu> <20041207141123.GA12025@elte.hu> <41B6839B.4090403@cybsft.com> <20041208083447.GB7720@elte.hu> <41B726D1.6030009@cybsft.com> <1102522720.30593.3.camel@krustophenia.net> <41B7314E.1050904@cybsft.com> Content-Type: text/plain Date: Wed, 08 Dec 2004 11:58:16 -0500 Message-Id: <1102525097.30593.20.camel@krustophenia.net> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2004-12-08 at 10:52 -0600, K.R. Foley wrote: > Lee Revell wrote: > > On Wed, 2004-12-08 at 10:07 -0600, K.R. Foley wrote: > > > >>I am still confused about one thing, unrelated to this. If RT tasks > >>never expire and thus are never moved to the expired array??? Does that > >>imply that we never switch the active and expired arrays? If so how do > >>tasks that do expire get moved back into the active array? > > > > > > I think that RT tasks use a completely different scheduling mechanism > > that bypasses the active/expired array. > > > > Lee > > > > > Please don't misunderstand. I am not arguing with you because obviously > I am not really intimate with this code, but if the above statement is > true then I am even more confused than I thought. I don't see any such > distinctions in the scheduler code. In fact it looks to me like the > whole scheduler is built on the premise of allowing RT tasks to be just > like other tasks with a few exceptions, one of which is that RT tasks > never hit the expired task array. No, you are probably right, I am the one who is confused. Lee