From: Andrew Morton <akpm@digeo.com>
To: uaca@alumni.uv.es
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.54-mm3
Date: Sun, 05 Jan 2003 12:38:16 -0800 [thread overview]
Message-ID: <3E1897B8.7688566B@digeo.com> (raw)
In-Reply-To: 20030105180446.GA20388@pusa.informat.uv.es
uaca@alumni.uv.es wrote:
>
> On Sat, Jan 04, 2003 at 01:00:38AM -0800, Andrew Morton wrote:
> >
> > http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.54/2.5.54-mm3/
>
> It seems to me that the patch you pointed here doesn't include the latency
> instrumentation.
No, it doesn't. You can monitor the latency using realfeel or realfeel2
from http://www.zip.com.au/~akpm/linux/amlat.tar.gz
But that won't tell you _why_ large latencies are occurring. For that,
you'll need to apply
http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.54/2.5.54-mm3/experimental/rtc-debug.patch
and run `amlat'. This combination will spit out stack backtraces whenever
there is a 2 millisecond scheduling overrun.
> Where it is the needed instrumentation to meassure it?
>
> In http://www.zip.com.au/~akpm/linux/ the are no timepeg/intlat patches for
> 2.5...
That's not suitable for this work. intlat is OK for locating and
measuring interrupts-off code paths. But it's a bit hard to drive.
next prev parent reply other threads:[~2003-01-05 20:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-04 9:00 2.5.54-mm3 Andrew Morton
2003-01-04 15:47 ` 2.5.54-mm3 Steven Barnhart
2003-01-04 21:18 ` 2.5.54-mm3 Andrew Morton
2003-01-04 22:31 ` 2.5.54-mm3 Steven Barnhart
2003-01-04 22:46 ` 2.5.54-mm3 Andrew Morton
2003-01-04 23:41 ` 2.5.54-mm3 Steven Barnhart
2003-01-05 18:04 ` 2.5.54-mm3 uaca
2003-01-05 20:38 ` Andrew Morton [this message]
2003-01-05 21:17 ` 2.5.54-mm3 uaca
-- strict thread matches above, loose matches on Subject: below --
2003-01-05 2:20 2.5.54-mm3 Steven Barnhart
2003-01-05 14:35 2.5.54-mm3 Michael Abshoff
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=3E1897B8.7688566B@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=uaca@alumni.uv.es \
/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