Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 2 Sep 2002 09:01:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 2 Sep 2002 09:01:27 -0400 Received: from pc1-cwma1-5-cust128.swa.cable.ntl.com ([80.5.120.128]:56569 "EHLO irongate.swansea.linux.org.uk") by vger.kernel.org with ESMTP id ; Mon, 2 Sep 2002 09:01:26 -0400 Subject: Re: Problem with the O(1) scheduler in 2.4.19 From: Alan Cox To: Tobias Ringstrom Cc: Ingo Molnar , Kernel Mailing List In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-6) Date: 02 Sep 2002 14:07:13 +0100 Message-Id: <1030972033.3490.57.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1061 Lines: 23 On Sun, 2002-09-01 at 22:53, Tobias Ringstrom wrote: > While the O(1) scheduler has performed very well for me in most > situations, I have one big problem with it. When running a Counter-Strike > game server on Linux 2.4.19 with the sched-2.4.19-rc2-A4 patch applied, > the server process is niced from the default value of 15 (interactive) to > 25 (background). This means that every time crond wakes up or a mail > arrives the game latency becomes extremely bad and the users experience > lag. > > The process takes around 70% CPU on these occasions, so I'm surprised that > the task is not considered to be interactive. > > This does not happen with stock 2.4.19. Do you have any ideas why this > regression is happening? It isnt a regression, its a bug fix. The nice value is now being honoured properly. - 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/