From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261551AbULIRc1 (ORCPT ); Thu, 9 Dec 2004 12:32:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261554AbULIRc1 (ORCPT ); Thu, 9 Dec 2004 12:32:27 -0500 Received: from mx1.elte.hu ([157.181.1.137]:13522 "EHLO mx1.elte.hu") by vger.kernel.org with ESMTP id S261551AbULIRcJ (ORCPT ); Thu, 9 Dec 2004 12:32:09 -0500 Date: Thu, 9 Dec 2004 18:31:36 +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: <20041209173136.GE7975@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: > >also, i'd like to take a look at latency traces, if you have them for > >this run. > > I could if I had any. The _RT run had NO latency traces > 250 usec > (the limit I had set for the test). The equivalent _PK run had 37 of > those traces. I can rerun the test with a smaller limit to get some if > it is really important. My build of -12 is almost done and we can see > what kind of repeatability / results from the all_cpus trace shows. /me is puzzled. so all the CPU-loop delays within the -RT kernel are below 250 usecs? I guess i dont understand what this means then: | 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? Ingo