Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264215AbUFFW7E (ORCPT ); Sun, 6 Jun 2004 18:59:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264211AbUFFW7E (ORCPT ); Sun, 6 Jun 2004 18:59:04 -0400 Received: from mail005.syd.optusnet.com.au ([211.29.132.54]:16004 "EHLO mail005.syd.optusnet.com.au") by vger.kernel.org with ESMTP id S264218AbUFFW6I (ORCPT ); Sun, 6 Jun 2004 18:58:08 -0400 From: Con Kolivas To: Felipe Alfaro Solana Subject: Re: [PATCH] Staircase Scheduler v6.3 for 2.6.7-rc2 Date: Mon, 7 Jun 2004 08:57:54 +1000 User-Agent: KMail/1.6.1 Cc: Linux Kernel Mailinglist , Zwane Mwaikambo , William Lee Irwin III References: <200406070139.38433.kernel@kolivas.org> <1086555593.1676.3.camel@teapot.felipe-alfaro.com> In-Reply-To: <1086555593.1676.3.camel@teapot.felipe-alfaro.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406070857.54785.kernel@kolivas.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1404 Lines: 29 On Mon, 7 Jun 2004 06:59, Felipe Alfaro Solana wrote: > On Sun, 2004-06-06 at 17:39, Con Kolivas wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > This is an update of the scheduler policy mechanism rewrite using the > > infrastructure of the current O(1) scheduler. Slight changes from the > > original design require a detailed description. The change to the > > original design has enabled all known corner cases to be abolished and > > cpu distribution to be much better maintained. It has proven to be stable > > in my testing and is ready for more widespread public testing now. > > It seems this staircase scheduler has some strange interactions with > networking and PM suspend. I can't suspend my laptop when any program is > using the network and, what's more, after the suspend mechanism fails, > the program that was using the network stays stuck at D state and can't > be killed. Could well be the autoregulated vm swappiness which triggers the unable to suspend when swappiness=0 bug. If not, this staircase scheduler is quite a large change to the scheduler priority design and there could be some weird interaction. 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/