From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261600AbULGOIP (ORCPT ); Tue, 7 Dec 2004 09:08:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261630AbULGOIP (ORCPT ); Tue, 7 Dec 2004 09:08:15 -0500 Received: from mx2.elte.hu ([157.181.151.9]:59608 "EHLO mx2.elte.hu") by vger.kernel.org with ESMTP id S261600AbULGOH5 (ORCPT ); Tue, 7 Dec 2004 09:07:57 -0500 Date: Tue, 7 Dec 2004 15:07:33 +0100 From: Ingo Molnar To: Mark_H_Johnson@raytheon.com Cc: Amit Shah , Karsten Wiese , Bill Huey , Adam Heath , emann@mrv.com, Gunther Persoons , "K.R. Foley" , linux-kernel@vger.kernel.org, Florian Schmidt , Fernando Pablo Lopez-Lezcano , Lee Revell , Rui Nuno Capela , Shane Shrybman , Esben Nielsen , Thomas Gleixner , Michal Schmidt Subject: Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm2-V0.7.32-0 Message-ID: <20041207140733.GA10072@elte.hu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-ELTE-SpamVersion: MailScanner 4.31.6-itk1 (ELTE 1.2) SpamAssassin 2.63 ClamAV 0.73 X-ELTE-VirusStatus: clean X-ELTE-SpamCheck: no X-ELTE-SpamCheck-Details: score=-2.201, required 5.9, BAYES_00 -4.90, SORTED_RECIPS 2.70 X-ELTE-SpamLevel: X-ELTE-SpamScore: -2 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org * Mark_H_Johnson@raytheon.com wrote: > > It is easy to hack the scheduler to fix some RT issue but break the > > generic scheduler - this solution is not meant to be such a hack. > > I agree but I see the big delay of running the RT task to be a symptom > that the current non RT scheduler is somehow broken. I've reported the > non RT starvation condition several times. Yes, the second CPU is > busy, but I really do want to bump cpu_burn (which is non RT & nice) > to run my (non RT and not nice) stress script / commands instead. well ... doing global balancing on SMP gets really expensive, really quick. It's simply not an option for 4 way or higher, and even on 2-way it's measurable. In the RT case arguably latency is more important than throughput, but i dont think the same case could be made for nice vs. non-nice. Ingo