RE: how to measure scheduler latency on powerpc? realfeel doesn' t work due to /dev/rtc issues

Perez-Gonzalez, Inaky
2003-05-13T01:55:52Z

> From: William Lee Irwin III [mailto:wli@holomorphy.com]
>
> From: William Lee Irwin III [mailto:wli@holomorphy.com]
> >> This is ridiculous. Just make sure you're not sharing interrupts and
> >> count cycles starting at the ISR instead of wakeup and tag events
> >> properly if you truly believe that to be your metric. You, as the
> >> kernel, are notified whenever the interrupts occur and can just look
> >> at the time of day and cycle counts.
>
> On Mon, May 12, 2003 at 05:20:39PM -0700, Perez-Gonzalez, Inaky wrote:
> > Well, I am only suggesting a way to _FORCE_ interrupts to happen
> > at a certain rate controllable by _SOMEBODY_, not as the system
> > gets them. Chris was concerned about not having a way to
> > _GENERATE_ interrupts at a certain rate.
> > What you are suggesting is the other part of the picture, how to
> > measure the latency and AFAICS, it is not part of the problem of
> > generating the interrupts.
>
> It also seems somewhat pointless to measure it under artificial
> conditions. Interrupts happen often anyway and you probably want to

Your artificial conditions are your control measurements. Then you
add the loads in the background; by being able to selectively add
and remove loads (the real live loads), then you can more easily
identify who is causing delays and under what conditions. It is
not as thorough as a full code analysis ... but if your coverage
is well done can help a lot.

But I am sure you know all this already.

Iñaky Pérez-González -- Not speaking for Intel -- all opinions are my own
(and my fault)