Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262410AbTEVAZ6 (ORCPT ); Wed, 21 May 2003 20:25:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262412AbTEVAZ6 (ORCPT ); Wed, 21 May 2003 20:25:58 -0400 Received: from imladris.surriel.com ([66.92.77.98]:13708 "EHLO imladris.surriel.com") by vger.kernel.org with ESMTP id S262410AbTEVAZ5 (ORCPT ); Wed, 21 May 2003 20:25:57 -0400 Date: Wed, 21 May 2003 20:38:56 -0400 (EDT) From: Rik van Riel To: Mike Galbraith cc: davidm@hpl.hp.com, "" , "" Subject: Re: web page on O(1) scheduler In-Reply-To: <5.2.0.9.2.20030521111037.01ed0d58@pop.gmx.net> Message-ID: References: <5.2.0.9.2.20030521111037.01ed0d58@pop.gmx.net> X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org 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: 936 Lines: 25 On Wed, 21 May 2003, Mike Galbraith wrote: > At 11:49 PM 5/20/2003 -0700, David Mosberger wrote: > >Recently, I started to look into some odd performance behaviors of the > >O(1) scheduler. I decided to document what I found in a web page > >at: > > > > http://www.hpl.hp.com/research/linux/kernel/o1.php > > The page mentions persistent starvation. My own explorations of this > issue indicate that the primary source is always selecting the highest > priority queue. It's deeper than that. The O(1) scheduler doesn't consider actual CPU usage as a factor of CPU priority. Rik -- Engineers don't grow up, they grow sideways. http://www.surriel.com/ http://kernelnewbies.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/