mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: Robert Love <rml@tech9.net>, linux-kernel@vger.kernel.org
Cc: kpreempt-tech@lists.sourceforge.net
Subject: Re: [PATCH] update: preemptive kernel for O(1) sched
Date: Tue, 15 Jan 2002 15:58:11 +0100	[thread overview]
Message-ID: <E16QVJC-0000uX-00@starship.berlin> (raw)
In-Reply-To: <1010961108.814.12.camel@phantasy> <1010982884.1527.52.camel@phantasy>
In-Reply-To: <1010982884.1527.52.camel@phantasy>

On January 14, 2002 05:34 am, Robert Love wrote:
> A version of preempt-stats for the 2.5 series kernel is available at:
> 
> 	ftp://ftp.kernel.org/pub/linux/kernel/people/rml/preempt-stats
> 
> and your favorite mirror.  Patches for 2.4 are available, too.
> 
> This patch, used on top of preempt-kernel, allows the measuring of
> periods of non-preemptible so that we can identify long-held locks.  The
> patch creates a proc entry, latencytimes, which contains the top 20
> worst-case recorded periods since it was last read.  To begin recording,
> read the file once.  Subsequent reads will return the results. I.e.,

Nice, but you need a way to turn it off, for example:

   echo >/proc/latencytimes

i.e., truncate.

> [23:25:08]rml@langston:~$ cat /proc/latencytimes 
> Worst 20 latency times of 277 measured in this period.
>   usec      cause     mask   start line/file      address   end line/file
>   9982  spin_lock        0   488/sched.c         c0117ee2   645/irq.c
>    968        BKL        0   666/tty_io.c        c0193d58   645/irq.c
>    430  spin_lock        0    69/i387.c          c010f34f    96/mmx.c
>    103       ide0        0   583/irq.c           c010ab1c   645/irq.c
>    100        BKL        0  2562/buffer.c        c014abda  2565/buffer.c
>     54        BKL        0   702/tty_io.c        c019406b   704/tty_io.c
> ... etc

A more typical form for the file/line would be, e.g., irq.c:645

> The goal would be to identity the problem areas and fix them.

Yep, sorry about the nits but that's the way we nitbots are programmed.

--
Daniel


  parent reply	other threads:[~2002-01-16 18:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-13 22:31 Robert Love
2002-01-14  4:34 ` Robert Love
2002-01-15 14:58   ` Daniel Phillips
2002-01-15 14:58   ` Daniel Phillips [this message]
2002-01-15 14:58   ` Daniel Phillips
2002-01-13 23:22 Dieter Nützel
     [not found] <200201132325.g0DNPrm05503@zero.tech9.net>
2002-01-13 23:48 ` Robert Love
2002-01-14  0:07   ` Dieter Nützel
2002-01-14  1:32   ` William Lee Irwin III
2002-01-15 19:48   ` 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=E16QVJC-0000uX-00@starship.berlin \
    --to=phillips@bonn-fries.net \
    --cc=kpreempt-tech@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.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

all inboxes | Powered by JetHome®