public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Mike Mattie <codermattie@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: recomended way to check longest period that interupts are disabled ?
Date: Thu, 26 Apr 2007 19:15:23 +0200	[thread overview]
Message-ID: <1177607723.25960.12.camel@localhost.localdomain> (raw)
In-Reply-To: <20070426051953.26582bbb@reforged>

On Thu, 2007-04-26 at 05:19 -0700, Mike Mattie wrote:
> Thanks for the comments. After running cyclictest it definitely looks
> like the average jitter is really low, around 7-8 . The max is really
> high , >100
> 
> If I am interpreting this correctly for the most part the jitter is
> pretty low, but something horrible is happening that blows up the
> max value.

Yup

> ./cyclictest -p 30 -t 6
> 2.00 1.84 1.41 3/120 13760
> 
> T: 0 (13130) P:30 I:1000 C:  42763 Min:      4 Act:   10 Avg:    8 Max:     133
> T: 1 (13131) P:29 I:1500 C:  28509 Min:      4 Act:    6 Avg:    7 Max:     114
> T: 2 (13132) P:28 I:2000 C:  21382 Min:      4 Act:    7 Avg:    6 Max:     157
> T: 3 (13133) P:27 I:2500 C:  17106 Min:      4 Act:   11 Avg:    7 Max:     110
> T: 4 (13134) P:26 I:3000 C:  14255 Min:      4 Act:    8 Avg:    7 Max:    1011
> T: 5 (13135) P:25 I:3500 C:  12218 Min:      4 Act:   12 Avg:    8 Max:     118

What happens with 

# cyclictest -p 80 -n

At first it puts the timer thread above everything else and second it
uses nanosleep instead of the signal delivered posix timers.

	tglx



      reply	other threads:[~2007-04-26 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26  9:13 recomended way to check longest period that interupts are disabled ? Mike Mattie
2007-04-26  9:53 ` Peter Zijlstra
     [not found]   ` <20070426040252.3f4fa8cc@reforged>
     [not found]     ` <1177585912.6815.6.camel@twins>
2007-04-26 12:19       ` Mike Mattie
2007-04-26 17:15         ` Thomas Gleixner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1177607723.25960.12.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=codermattie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox