Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262278AbUKDQSF (ORCPT ); Thu, 4 Nov 2004 11:18:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262281AbUKDQSF (ORCPT ); Thu, 4 Nov 2004 11:18:05 -0500 Received: from mx1.elte.hu ([157.181.1.137]:10134 "EHLO mx1.elte.hu") by vger.kernel.org with ESMTP id S262278AbUKDQR7 (ORCPT ); Thu, 4 Nov 2004 11:17:59 -0500 Date: Thu, 4 Nov 2004 17:17:56 +0100 From: Ingo Molnar To: Mark_H_Johnson@raytheon.com Cc: Karsten Wiese , Bill Huey , Adam Heath , "K.R. Foley" , linux-kernel@vger.kernel.org, Florian Schmidt , Fernando Pablo Lopez-Lezcano , Lee Revell , Rui Nuno Capela , Thomas Gleixner , Michal Schmidt Subject: Re: [patch] Real-Time Preemption, -RT-2.6.10-rc1-mm2-V0.7.1 Message-ID: <20041104161756.GA2002@elte.hu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-ELTE-SpamVersion: MailScanner 4.31.6-itk1 (ELTE 1.2) SpamAssassin 2.63 ClamAV 0.73 X-ELTE-VirusStatus: clean X-ELTE-SpamCheck: no X-ELTE-SpamCheck-Details: score=-2.201, required 5.9, BAYES_00 -4.90, SORTED_RECIPS 2.70 X-ELTE-SpamLevel: X-ELTE-SpamScore: -2 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1118 Lines: 24 * 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/