From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261241AbULMW4x (ORCPT ); Mon, 13 Dec 2004 17:56:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261204AbULMWyi (ORCPT ); Mon, 13 Dec 2004 17:54:38 -0500 Received: from mx2.elte.hu ([157.181.151.9]:27868 "EHLO mx2.elte.hu") by vger.kernel.org with ESMTP id S261338AbULMWkn (ORCPT ); Mon, 13 Dec 2004 17:40:43 -0500 Date: Mon, 13 Dec 2004 23:39:47 +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-mm3-V0.7.32-15 Message-ID: <20041213223947.GB6944@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: > The maximum duration of the CPU loop (as measured by the application) > is in the range of 1.42 msec to 2.57 compared to the nominal 1.16 msec > duration for -20RT. The equivalent numbers for -20PK are 1.28 to 1.93 > msec. [...] so -20RT has resolved all the CPU-loop-max-delay issues of the -RT kernel regarding the RT-priority CPU loop and in essence adds only a small amount of delay (100 usecs?) to the nominal (==minimum possible) delay? i suspect the 100 usecs comparison is an effect of the cutoff value being a single value. Also, 100 usecs is so close to the DMA related delay which makes it hard to compare it - other than stating that -RT has higher CPU overhead. are the ping times still considered anomalous? Could be a side-effect of the different flow of control between hardirq/softirq contexts. (There have been a (low but nonzero) number of assumptions about the flow in pieces of softirq code, and there could be more.) Ingo