Messages in this thread | | | Date | Sun, 21 Nov 2004 16:05:25 +0100 | From | Florian Schmidt <> | Subject | Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm2-V0.7.29-0 |
| |
On Sun, 21 Nov 2004 14:43:54 +0100 Ingo Molnar <mingo@elte.hu> wrote:
> on a 2 GHz UP box the worst-case max jitter i can trigger via rtc_wakeup > is 11 usecs, using the -5 kernel. The workload i used was 40 parallel > copies of LTP plus a few hackbench runs. This is how i started > rtc_wakeup: > > chrt -f 80 -p `pidof 'IRQ 0'` > chrt -f 98 -p `pidof 'IRQ 8'` > > cd rtc_wakeup > ./rtc_wakeup -f 1024 -t 100000 > > i.e. IRQ0 is below IRQ8 and the rtc_wakeup threads, but above every > other IRQ thread. Here's the histogram of a short (~5 minutes) run:
Ah, ok, this makes sense.. Will try the same. Btw: one more question wrt the IRQ prios:
Let's assume i have IRQ 0 at 80, my soundcard and the rtc irq both at prio 98 and all others around 40. Now the rtc handler should never get in the way of the soundcard irq if the rtc is simply not used right? And of course, the other way around, too. the soundcard irq should not get in the way of the rtc handler if the soundcard simply is not used and not generating IRQ's?
> > 1 247383 > 2 34842 > 3 1488 > 4 3188 > 5 125 > 6 1 > > so this a 6 usecs max delay measured by /dev/rtc. So on your box, if the > max histogram delay was 16 usecs, i'd not expect a worse than ~30 usecs > jitter measured by rtc_wakeup. Can you reproduce the 150 usecs jitter > with the above IRQ setup?
not yet.
flo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |