Messages in this thread | | | Date | Thu, 4 Nov 2004 17:17:56 +0100 | From | Ingo Molnar <> | Subject | Re: [patch] Real-Time Preemption, -RT-2.6.10-rc1-mm2-V0.7.1 |
| |
* Mark_H_Johnson@raytheon.com <Mark_H_Johnson@raytheon.com> wrote:
> >does the ping phenomenon go away if you chrt both the networking IRQ > >thread and both ksoftirqd's to above the RT task's priority? > > For the most part, yes. I reran the test with -V0.7.7 and had > continuous ping responses until the system locked up with yet another > deadlock. This did NOT fix the display / mouse movement lockups. All > IRQ and ksoftirqd tasks were RT 99 priority for this test. latencytest > ran at RT 30 priority.
another method would be to set all smp_affinity values in /proc/irq/*/ to 1 (i.e. let CPU#0 handle all IRQs), and start latencytest on CPU#1, via 'taskset'. In theory this should ensure that no hardirq workload runs on CPU#1 and thus ksoftirqd would not be active there either. (with the exception of kernel timers started on that CPU, by latencytest.)
Ingo - 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/
| |