From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261606AbULIUQU (ORCPT ); Thu, 9 Dec 2004 15:16:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261605AbULIUQT (ORCPT ); Thu, 9 Dec 2004 15:16:19 -0500 Received: from viper.oldcity.dca.net ([216.158.38.4]:36568 "HELO viper.oldcity.dca.net") by vger.kernel.org with SMTP id S261604AbULIUQP (ORCPT ); Thu, 9 Dec 2004 15:16:15 -0500 Subject: Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm3-V0.7.32-6 From: Lee Revell To: Esben Nielsen Cc: Mark_H_Johnson@raytheon.com, Florian Schmidt , Amit Shah , Karsten Wiese , Bill Huey , Adam Heath , emann@mrv.com, Gunther Persoons , "K.R. Foley" , linux-kernel@vger.kernel.org, Ingo Molnar , Fernando Pablo Lopez-Lezcano , Rui Nuno Capela , Shane Shrybman , Thomas Gleixner , Michal Schmidt In-Reply-To: References: Content-Type: text/plain Date: Thu, 09 Dec 2004 15:16:13 -0500 Message-Id: <1102623373.21688.6.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 Thu, 2004-12-09 at 20:04 +0100, Esben Nielsen wrote: > IRQ threading makes the system more predictable but for many, many > devices it is very expensive. I am predicting that many interrupt routines > have to be turned back to running in interrupt context. It's important to keep in mind that for the type of applications that would want PREEMPT_DESKTOP, the IRQ threading is only necessary because of the amount of work the IDE subsystem does in hardirq context. There was some discussion a while back and Jens posted a patch to move the IDE IO completion to a softirq. IIRC there was not a lot of comment on it. But, it seems to me that this approach would give the most favorable balance of performance and low latency for many uses. My tests show that with softirq preemption this should allow jackd to run at 64 frames or so without IRQ threading. Lee