Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 30 Mar 2003 09:03:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 30 Mar 2003 09:03:22 -0500 Received: from ns.virtualhost.dk ([195.184.98.160]:51419 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id ; Sun, 30 Mar 2003 09:03:21 -0500 Date: Sun, 30 Mar 2003 16:14:04 +0200 From: Jens Axboe To: Robert Love Cc: Con Kolivas , Felipe Alfaro Solana , Peter Lundkvist , akpm@digeo.com, mingo@elte.hu, LKML Subject: Re: Bad interactive behaviour in 2.5.65-66 (sched.c) Message-ID: <20030330141404.GG917@suse.de> References: <3E8610EA.8080309@telia.com> <1048987260.679.7.camel@teapot> <1048989922.13757.20.camel@localhost> <200303301233.03803.kernel@kolivas.org> <1048992365.13757.23.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1048992365.13757.23.camel@localhost> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1041 Lines: 26 On Sat, Mar 29 2003, Robert Love wrote: > On Sat, 2003-03-29 at 21:33, Con Kolivas wrote: > > > Are you sure this should be called a bug? Basically X is an interactive > > process. If it now is "interactive for a priority -10 process" then it should > > be hogging the cpu time no? The priority -10 was a workaround for lack of > > interactivity estimation on the old scheduler. > > Well, I do not necessarily think that renicing X is the problem. Just > an idea. I see the exact same behaviour here (systems appears fine, cpu intensive app running, attempting to start anything _new_ stalls for ages), and I definitely don't play X renice tricks. It basically made 2.5 unusable here, waiting minutes for an ls to even start displaying _anything_ is totally unacceptable. -- Jens Axboe - 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/