From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030945AbXDQXJ7 (ORCPT ); Tue, 17 Apr 2007 19:09:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030930AbXDQXJ6 (ORCPT ); Tue, 17 Apr 2007 19:09:58 -0400 Received: from holomorphy.com ([66.93.40.71]:35301 "EHLO holomorphy.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030929AbXDQXJy (ORCPT ); Tue, 17 Apr 2007 19:09:54 -0400 Date: Tue, 17 Apr 2007 16:07:54 -0700 From: William Lee Irwin III To: "Michael K. Edwards" Cc: Peter Williams , Ingo Molnar , Nick Piggin , Mike Galbraith , Con Kolivas , ck list , Bill Huey , linux-kernel@vger.kernel.org, Linus Torvalds , Andrew Morton , Arjan van de Ven , Thomas Gleixner Subject: Re: [Announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS] Message-ID: <20070417230754.GR2986@holomorphy.com> References: <200704151327.13589.kernel@kolivas.org> <1176619384.6222.70.camel@Homer.simpson.net> <46240F98.3020800@bigpond.net.au> <1176776941.6222.21.camel@Homer.simpson.net> <20070417034050.GD25513@wotan.suse.de> <1176782489.13059.15.camel@Homer.simpson.net> <20070417041420.GF25513@wotan.suse.de> <20070417095140.GB22626@elte.hu> <4624CF3B.6040704@bigpond.net.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: The Domain of Holomorphy User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 17, 2007 at 04:00:53PM -0700, Michael K. Edwards wrote: > Works, that is, right up until you add nonlinear interactions with CPU > speed scaling. From my perspective as an embedded platform > integrator, clock/voltage scaling is the elephant in the scheduler's > living room. Patch in DPM (now OpPoint?) to scale the clock based on > what task is being scheduled, and suddenly the dynamic priority > calculations go wild. Nip this in the bud by putting an RT priority > on the relevant threads (which you have to do anyway if you need > remotely audio-grade latency), and the lock affinity heuristics break, > so you have to hand-tune all the thread priorities. Blecch. [...not terribly enlightening stuff trimmed...] The ongoing scheduler work is on a much more basic level than these affairs I'm guessing you googled. When the basics work as intended it will be possible to move on to more advanced issues. -- wli