Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261617AbUJaNVn (ORCPT ); Sun, 31 Oct 2004 08:21:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261622AbUJaNVn (ORCPT ); Sun, 31 Oct 2004 08:21:43 -0500 Received: from mx1.elte.hu ([157.181.1.137]:18085 "EHLO mx1.elte.hu") by vger.kernel.org with ESMTP id S261617AbUJaNVk (ORCPT ); Sun, 31 Oct 2004 08:21:40 -0500 Date: Sun, 31 Oct 2004 14:22:37 +0100 From: Ingo Molnar To: Florian Schmidt Cc: Lee Revell , Paul Davis , Thomas Gleixner , LKML , mark_h_johnson@raytheon.com, Bill Huey , Adam Heath , Michal Schmidt , Fernando Pablo Lopez-Lezcano , Karsten Wiese , jackit-devel , Rui Nuno Capela Subject: Re: [Fwd: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4] Message-ID: <20041031132237.GB23437@elte.hu> References: <20041030214738.1918ea1d@mango.fruits.de> <1099165925.1972.22.camel@krustophenia.net> <20041030221548.5e82fad5@mango.fruits.de> <1099167996.1434.4.camel@krustophenia.net> <20041030231358.6f1eeeac@mango.fruits.de> <1099171567.1424.9.camel@krustophenia.net> <20041030233849.498fbb0f@mango.fruits.de> <20041031120721.GA19450@elte.hu> <20041031124828.GA22008@elte.hu> <20041031151130.675cb012@mango.fruits.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041031151130.675cb012@mango.fruits.de> 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=-4.9, required 5.9, autolearn=not spam, BAYES_00 -4.90 X-ELTE-SpamLevel: X-ELTE-SpamScore: -4 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2056 Lines: 51 * Florian Schmidt wrote: > also, i have uploaded an overhauled version of the wakeup timer > program. It now deferres all output to another SCHED_FIFO thread [with > prio 1 lower than the main process]. The data is passed via a lockless > fifo [ripped from jack sourcecode]. Also it handles commandline > options better and has sensible [?] defaults: > > ~/source/my_projects/wakeup$ ./rtc_wakeup -h > usage: wakeup [options] > options: > -f freqency(hz) (default 1024) > -p realtime prio (default 90(91)) > -n max number of interrupts (default 0: run until stopped) > -t jitter threshold (%) (default 5) > -o history_file (default /dev/null) > -h show help cool! May i have a feature request :-) It would be quite useful to have an option to see the jitter output in percentage and in microseconds as well. I.e. an option to have such a format: late wakeup: +151.3 usecs (14.6%) jitter. cycles are too large to be human readable, and absolute values are harder to read when HZ is not 1024. So to get a 'quick feel' of the delays in a system the above line would be the most informative (for me that is). Also, the percentage can go back to %.1f i think, instead of %.5f or so - it's good to have a decimal point in the percentage but one number after it is more than enough.) The more compact the output, the fewer useless info, the quicker the human brain can read it. (Obviously to generate a nice graph out of it needs a different format.) > Here's a typical run (still on V0.5.16, will try V0.6 now): please try -V0.6.1, -V0.6 had a pretty stupid bug that could trigger frequently. > threshold violations: 20 > max jitter: 58.1228% here it would also be useful to have the 'max jitter' in usecs. I.e. in the above case it was somewhere around ~570 usecs. Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/