Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753230AbZJZSXH (ORCPT ); Mon, 26 Oct 2009 14:23:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752935AbZJZSXG (ORCPT ); Mon, 26 Oct 2009 14:23:06 -0400 Received: from cavan.codon.org.uk ([93.93.128.6]:56686 "EHLO cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752854AbZJZSXF (ORCPT ); Mon, 26 Oct 2009 14:23:05 -0400 Date: Mon, 26 Oct 2009 18:23:04 +0000 From: Matthew Garrett To: Robert Bradbury Cc: linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org Subject: Re: Broken ondemand scheduler in Linux 2.6.30+ on Pentium IVs Message-ID: <20091026182304.GB4657@srcf.ucam.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: mjg59@cavan.codon.org.uk X-SA-Exim-Scanned: No (on cavan.codon.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 716 Lines: 16 ...except that conservative has the same latency threshold as ondemand, which I'm sure wasn't supposed to be the case. I've added the cpufreq list to Cc:. (Summary: p4-clockmod had its latency changed to avoid ondemand using it, which was done to avoid the performance impact that ondemand generates on p4s. I thought that conservative was still supposed to work here, but as it has the same latency threshold it doesn't) -- Matthew Garrett | mjg59@srcf.ucam.org -- 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/