From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261601AbULIULe (ORCPT ); Thu, 9 Dec 2004 15:11:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261602AbULIULe (ORCPT ); Thu, 9 Dec 2004 15:11:34 -0500 Received: from mx2.elte.hu ([157.181.151.9]:33955 "EHLO mx2.elte.hu") by vger.kernel.org with ESMTP id S261601AbULIUL2 (ORCPT ); Thu, 9 Dec 2004 15:11:28 -0500 Date: Thu, 9 Dec 2004 21:11:10 +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-6 Message-ID: <20041209201110.GB14194@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 max CPU latencies in RT are worse than PK as well. The values for > >| RT range from 3.00 msec to 5.43 msec and on PK range from 1.45 msec to > >| 2.24 msec. > > > > > >these come from userspace timestamping? So where userspace detects a > >delay the kernel tracer doesnt measure any? > > Yes. That is correct. Very puzzling to me too. well, i think this measurement issue needs resolving before jumping to any generic conclusions. Not a single trace is extremely suspect. The userspace timestamps are rdtsc based, or gettimeofday() based? In theory, as long as no trace is triggered, there should not be any huge overhead from tracing itself (when a trace is reported and saved then, if the trace is large, it can be quite expensive that the tracer wont report as a latency - but this isnt the case here). Ingo