Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S272701AbTG1HeW (ORCPT ); Mon, 28 Jul 2003 03:34:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S272702AbTG1HeW (ORCPT ); Mon, 28 Jul 2003 03:34:22 -0400 Received: from mx1.elte.hu ([157.181.1.137]:32427 "EHLO mx1.elte.hu") by vger.kernel.org with ESMTP id S272701AbTG1HeV (ORCPT ); Mon, 28 Jul 2003 03:34:21 -0400 Date: Mon, 28 Jul 2003 09:44:37 +0200 (CEST) From: Ingo Molnar Reply-To: Ingo Molnar To: Mike Galbraith Cc: Con Kolivas , Felipe Alfaro Solana , LKML Subject: Re: [patch] sched-2.6.0-test1-G6, interactivity changes In-Reply-To: <5.2.1.1.2.20030728093215.01be8f68@pop.gmx.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1237 Lines: 32 On Mon, 28 Jul 2003, Mike Galbraith wrote: > >Yes I can reproduce it, but we need the Kirk approach and cheat. Some > >workaround for tasks that have fallen onto the expired array but shouldn't be > >there needs to be created. But first we need to think of one before we can > >create one... > > Oh good, it's not my poor little box. My experimental tree already has > a "Kirk" ;-) could you give -G7 a try: redhat.com/~mingo/O(1)-scheduler/sched-2.6.0-test1-G7 Mr. Kirk was busy fixing the IDE code (a subsystem he loves to contribute to) but i managed to get some code from Mr. Spock: it introduces ON_RUNQUEUE_WEIGHT, set to 30% currently. Wakeups that come from IRQ contexts get a 100% sleep average - most hw interrupts are of interactive nature. this method should result in process-context wakeups giving a limited but load-proportional boost - which boost is enough to prevent such tasks from getting max CPU hogs, but not enough to make them permanently interactive. 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/