public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Andre Pang <ozone@algorithm.com.au>
Cc: linux-kernel@vger.kernel.org, safemode@speakeasy.net,
	Dieter.Nuetzel@hamburg.de, iafilius@xs4all.nl,
	ilsensine@inwind.it, george@mvista.com
Subject: Re: [PATCH] Preemption Latency Measurement Tool
Date: 22 Sep 2001 02:10:18 -0400	[thread overview]
Message-ID: <1001139027.1245.28.camel@phantasy> (raw)
In-Reply-To: <1001131036.557760.4340.nullmailer@bozar.algorithm.com.au>
In-Reply-To: <1000939458.3853.17.camel@phantasy>  <1001131036.557760.4340.nullmailer@bozar.algorithm.com.au>

On Fri, 2001-09-21 at 23:57, Andre Pang wrote:
> hi Robert, thanks for producing the stats patches!

no problem, but note that the original work was by MontaVista.  They
have contributed a lot to lowering latency in the Linux kernel.

I just spruced the patch up and updated it for the current kernels.

> i did a test of it on linux-2.4.10-pre13 with Benno Senoner's
> lowlatency program, which i hacked up a bit to output
> /proc/latencytimes after each of the graphs.  test results are at
> 
>     http://www.algorithm.com.au/hacking/linux-lowlatency/2.4.10-pre13-pes/
> 
> and since i stared at the results in disbelief, i won't even try
> to guess what's going on :).  maybe you can make some sense of
> it?

Well, its not hard to decipher...and really, its actually fairly good.
the latency test program is giving you a max latency of around 12ms in
each test, which is OK.

the preemption-test patch is showing _MAX_ latencies of 0.8ms through
12ms.  this is fine, too.

> i'm prety sure his latencytest program runs at real-time
> priority, but i'll run another test just with the getrt and rt
> programs just posted to the list to make sure.  that's the only
> reason i can think why the graph is so bizarre compared to the
> /proc/latencytimes results.

well, latencytest is showing you the end result of a certain set of
operations, with a final latency of 12ms.  the /proc interface is a bit
more specific, in that it shows you latencies over individual locks.

the latencies over the specific locks held during latencytest, plus the
time to execute the instructions outside of locks, is equal to 12ms. 
the correlation between max lock and latencytest is not 1-to-1.

in an ideal world, you want latencytest to show you 10ms or less, which
we are pretty close to by your results, and you want most of your locks
under 1ms, which we also achieve since of your top 20 locks out of 20k+,
we see many still around 1ms.

thank you for these data points...

-- 
Robert M. Love
rml at ufl.edu
rml at tech9.net


  reply	other threads:[~2001-09-22  6:10 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-19 22:44 [PATCH] Preemption Latency Measurement Tool Robert Love
2001-09-20  1:40 ` Ignacio Vazquez-Abrams
2001-09-20  2:23   ` safemode
2001-09-20  1:13     ` David Lang
2001-09-20  2:57       ` Robert Love
2001-09-20  2:38     ` Robert Love
2001-09-20  6:31 ` Dieter Nützel
2001-09-20  6:31 ` Dieter Nützel
2001-09-20 20:27   ` Robert Love
     [not found]     ` <200109202111.f8KLBgG16833@zero.tech9.net>
2001-09-20 22:09       ` [PATCH] Preemption patch 2.4.9-ac12 Robert Love
     [not found] ` <20010920063143.424BD1E41A@Cantor.suse.de>
2001-09-20  6:41   ` [PATCH] Preemption Latency Measurement Tool Andrea Arcangeli
2001-09-20  7:57     ` Dieter Nützel
     [not found]     ` <20010920075751.6CA791E6B2@Cantor.suse.de>
2001-09-20  8:21       ` Andrea Arcangeli
2001-09-20 20:13         ` george anzinger
2001-09-20 20:38           ` Randy.Dunlap
2001-09-20 21:10         ` Robert Love
2001-09-20 21:35           ` Dieter Nützel
2001-09-20 22:03             ` Oliver Xymoron
2001-09-20 22:51               ` Dieter Nützel
     [not found]               ` <200109202252.f8KMqLG17327@zero.tech9.net>
2001-09-21  3:17                 ` Robert Love
2001-09-21 15:48                   ` george anzinger
2001-09-22 21:09                     ` Dieter Nützel
2001-09-22 23:40                       ` safemode
2001-09-22 23:46                       ` Dieter Nützel
2001-09-23  0:15                       ` safemode
     [not found]                       ` <200109222340.BAA37547@blipp.internet5.net>
2001-09-23  0:38                         ` Roger Larsson
2001-09-23  1:42                           ` safemode
2001-09-23  3:02                           ` Robert Love
2001-09-23 16:43                             ` Roger Larsson
2001-09-23  0:42                       ` Dieter Nützel
     [not found]                       ` <200109222341.f8MNfnG25152@zero.tech9.net>
2001-09-23  2:50                         ` Robert Love
2001-09-23  3:14                           ` george anzinger
2001-09-23  4:06                             ` Dieter Nützel
     [not found]                       ` <200109222347.f8MNlMG25157@zero.tech9.net>
2001-09-23  2:54                         ` Robert Love
2001-09-27  0:02                           ` [reiserfs-list] " Dieter Nützel
     [not found]                       ` <200109230016.f8N0G6G25222@zero.tech9.net>
2001-09-23  2:58                         ` Robert Love
     [not found]                     ` <200109222120.f8MLKYG24859@zero.tech9.net>
2001-09-23  2:44                       ` Robert Love
     [not found]     ` <200109200757.JAA60995@blipp.internet5.net>
2001-09-20 17:37       ` Roger Larsson
2001-09-20 21:29         ` Robert Love
2001-09-20 21:53           ` Dieter Nützel
     [not found]     ` <200109200758.f8K7wEG13675@zero.tech9.net>
2001-09-20 21:09       ` Robert Love
2001-09-20 20:01 ` Tobias Diedrich
2001-09-20 22:01   ` Robert Love
2001-09-22  3:57 ` Andre Pang
2001-09-22  6:10   ` Robert Love [this message]
2001-09-22  7:22     ` Andre Pang
2001-09-23  3:18       ` george anzinger
2001-09-23  3:21         ` Robert Love
2001-09-23  7:05       ` Robert Love
2001-09-23 12:03         ` Andre Pang
2001-09-23 18:31           ` Robert Love
2001-09-22 12:56     ` ksoftirqd? (Was: Re: [PATCH] Preemption Latency Measurement Tool) Roger Larsson
2001-09-22 13:14       ` Andrea Arcangeli
2001-09-22 20:51         ` Roger Larsson
2001-09-22 21:33           ` Andrea Arcangeli
     [not found] <200109202253.RAA21082@waste.org>
2001-09-20 23:15 ` [PATCH] Preemption Latency Measurement Tool Oliver Xymoron
2001-09-21  0:42   ` Roger Larsson
2001-09-21  1:03     ` Alan Cox
2001-09-21  1:22       ` Andrea Arcangeli
2001-09-21  1:51         ` Rik van Riel
2001-09-21  1:38       ` Roger Larsson
2001-09-21  1:53         ` Roger Larsson
2001-09-21  2:08           ` Roger Larsson
2001-09-21  2:29             ` Rik van Riel
2001-09-21 16:24       ` Jussi Laako
2001-09-21 16:36         ` Alan Cox
2001-09-21 18:46         ` Thomas Sailer
2001-09-22 10:30           ` Jussi Laako
2001-09-21 16:18     ` Stefan Westerfeld
2001-09-21 20:18       ` Dieter Nützel
     [not found]       ` <200109212018.f8LKImG21229@zero.tech9.net>
2001-09-21 21:47         ` Robert Love
  -- strict thread matches above, loose matches on Subject: below --
2002-04-09  5:23 [PATCH] preemption latency measurement tool Robert Love

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=1001139027.1245.28.camel@phantasy \
    --to=rml@tech9.net \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=george@mvista.com \
    --cc=iafilius@xs4all.nl \
    --cc=ilsensine@inwind.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ozone@algorithm.com.au \
    --cc=safemode@speakeasy.net \
    /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