Re: Real-Time Preemption, -RT-2.6.10-rc2-mm3-V0.7.31-13

[K.R. Foley]

Gene Heskett wrote:
> On Monday 29 November 2004 20:50, K.R. Foley wrote:
>
> > Gene Heskett wrote:
>
>
> > > > make that -31-13 (or later). Earlier kernels had a bug in where
>
>
> [...]
>
>
> > Is this all that is in the log? For some reason there are 820
> > samples not represented in the output above. The ms+ hits would
> > have been represented by something like:
> >
> > Nov 29 18:05:45 coyote kernel: 9999 4
>
>
> Ok, I finally got -13 to run (typo in grub), and you are now correct 
> in that the final entry in the log after I shut tvtime down is like 
> this:
>
> Nov 29 23:43:40 coyote kernel: rtc latency histogram of {tvtime/3911, 
> 10430 samples}:
> Nov 29 23:43:40 coyote kernel: 4 51
> Nov 29 23:43:40 coyote kernel: 5 2058
> Nov 29 23:43:40 coyote kernel: 6 3594
> Nov 29 23:43:40 coyote kernel: 7 1270
> Nov 29 23:43:40 coyote kernel: 8 473
> Nov 29 23:43:40 coyote kernel: 9 299
> Nov 29 23:43:40 coyote kernel: 10 252
> Nov 29 23:43:40 coyote kernel: 11 209
> Nov 29 23:43:40 coyote kernel: 12 215
> Nov 29 23:43:40 coyote kernel: 13 345
> Nov 29 23:43:40 coyote kernel: 14 391
> Nov 29 23:43:40 coyote kernel: 15 248
> Nov 29 23:43:40 coyote kernel: 16 113
> Nov 29 23:43:40 coyote kernel: 17 55
> Nov 29 23:43:40 coyote kernel: 18 17
> Nov 29 23:43:40 coyote kernel: 19 11
> Nov 29 23:43:40 coyote kernel: 20 4
> Nov 29 23:43:40 coyote kernel: 21 1
> Nov 29 23:43:40 coyote kernel: 23 2
> Nov 29 23:43:40 coyote kernel: 28 1
> Nov 29 23:43:40 coyote kernel: 4612 1
> Nov 29 23:43:40 coyote kernel: 9999 820
>
> What does this tell you now?  The last 2 lines look a bit strange to
> me.  Particularly since the runtime was random enough that your 
> previous comment about the number 820 was a mssing count, and what 
> came out of a seperate run IS an 820.
>
> I find that a bit hard to believe that I timed those two runs 
> identically.

When I mentioned 820 that was just what was missing from the histogram 
data vs. the total samples. As for why this number showed up again, dumb 
luck? What the histogram represents is usecs (left column) between 
interrupt and read. The right column is the number of occurrences. What 
this tells me is that you had 820 samples that were greater than 9.999ms.

I took a brief look at the tvtime code. I noticed several things:
1) tvtime sets the interrupt frequency for the rtc to 1024 Hz which 
would imply that you should have had roughly 30000 samples in a 30 
second run, minus initial setup time. The histogram only shows 10430 
samples. I have no way of knowing if the setup time is really that long 
or if you are missing some interrupts. Unfortunately the rtc histogram 
stuff doesn't currently track missed interrupts except to print out the 
messages you were seeing

"<some process> is being piggy... Read missed before next interrupt"

2) tvtime is probably running at a RT priority of 99. The IRQ handler 
for the rtc defaults to 48-49 (I think). If you didn't already do so, 
you should bump the priority up as in:

chrt -f -p 99 `/sbin/pidof 'IRQ 8'`

Try that and see if it helps at all.

kr
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/