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

[William Lee Irwin III <wli@holomorphy.com>]

William Lee Irwin III wrote:
>>> I don't understand why you're obsessed with interrupts. Just run your
>>> load and spray the scheduler latency stats out /proc/

From: Chris Friesen [mailto:cfriesen@nortelnetworks.com]
>> I'm obsessed with interrupts because it gives me a higher sampling rate.
>> I could set up and itimer for a recurring 10ms timeout and see how much
>> extra I waited, but then I can only get 100 samples/sec. With
>> /dev/rtc (on intel) you can get 20x more samples in the same amount
>> of time.

On Fri, May 09, 2003 at 05:39:03PM -0700, Perez-Gonzalez, Inaky wrote:
> Okay, crazy idea here ...
> You are talking about a bladed system, right? So probably you
> have two network interfaces in there [it should work only with
> one too].
> What if you rip off the driver for the network interface and 
> create a new breed. Set an special link with a null Ethernet
> cable and have one machine sending really short Ethernet frames

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.


-- wli