Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261417AbVAaXAj (ORCPT ); Mon, 31 Jan 2005 18:00:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261418AbVAaXAi (ORCPT ); Mon, 31 Jan 2005 18:00:38 -0500 Received: from mail02.syd.optusnet.com.au ([211.29.132.183]:28804 "EHLO mail02.syd.optusnet.com.au") by vger.kernel.org with ESMTP id S261417AbVAaXAK (ORCPT ); Mon, 31 Jan 2005 18:00:10 -0500 Message-ID: <41FEB8BA.7000106@kolivas.org> Date: Tue, 01 Feb 2005 10:01:14 +1100 From: Con Kolivas User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Jack O'Quin" Cc: linux kernel , Andrew Morton , Ingo Molnar , Alexander Nyberg , Zwane Mwaikambo Subject: Re: [PATCH] sched - Implement priority and fifo support for SCHED_ISO References: <41F76746.5050801@kolivas.org> <87acqpjuoy.fsf@sulphur.joq.us> <41FE9582.7090003@kolivas.org> <87651di55a.fsf@sulphur.joq.us> In-Reply-To: <87651di55a.fsf@sulphur.joq.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1371 Lines: 41 Jack O'Quin wrote: > Con Kolivas writes: > > >>Sure enough I found the bug in less than 5 mins, and it would >>definitely cause this terrible behaviour. >> >>A silly bracket transposition error on my part :P > > > The corrected version works noticeably better, but still nowhere near > as well as SCHED_FIFO. The first run had a cluster of really bad > xruns. The second and third were much better, but still with numerous > small xruns. > > http://www.joq.us/jack/benchmarks/sched-iso-fix/ > > With a compile running in the background it was a complete failure. > Some kind of big xrun storm triggered a collapse on every attempt. > > http://www.joq.us/jack/benchmarks/sched-iso-fix+compile/ > > The summary statistics are mixed. The delay_max is noticeably better > than before, but still much worse than SCHED_FIFO. But, the xruns are > really bad news... Excellent. Believe it or not these look like good results to me. Your XRUNS are happening when the DSP load is >70% which is the iso_cpu % cutoff. Try setting the iso_cpu to 90% echo 90 > /proc/sys/kernel/iso_cpu Cheers, Con - 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/