Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261998AbTFBH0j (ORCPT ); Mon, 2 Jun 2003 03:26:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262000AbTFBH0j (ORCPT ); Mon, 2 Jun 2003 03:26:39 -0400 Received: from mx1.elte.hu ([157.181.1.137]:32228 "EHLO mx1.elte.hu") by vger.kernel.org with ESMTP id S261998AbTFBH0i (ORCPT ); Mon, 2 Jun 2003 03:26:38 -0400 Date: Mon, 2 Jun 2003 09:39:34 +0200 (CEST) From: Ingo Molnar Reply-To: Ingo Molnar To: Tom Sightler Cc: Mike Galbraith , Andrew Morton , LKML Subject: Re: Strange load issues with 2.5.69/70 in both -mm and -bk trees. In-Reply-To: <1054489407.1722.50.camel@iso-8590-lx.zeusinc.com> Message-ID: 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: 1262 Lines: 35 On 1 Jun 2003, Tom Sightler wrote: > Yes, this is correct. It's showed as pluginserver in the 'ps ax' output > but I've since noticed that it is simply a symlink to wine. Of the two > wine processes, wine and wineserver, it was the wine frontend process > that was getting all of the CPU, showing 100% utilization. Renicing the > wine process made the problem go away. > > Running the exact same config on a 2.4.20 kernel uses only a few % of > the CPU. could you apply the attached patch to 2.5.70 and check whether wine still uses up 100% CPU time? This might be an artifact introduced by the different HZ values of 2.4 and 2.5. Ingo --- include/asm-i386/param.h.orig +++ include/asm-i386/param.h @@ -2,7 +2,7 @@ #define _ASMi386_PARAM_H #ifdef __KERNEL__ -# define HZ 1000 /* Internal kernel timer frequency */ +# define HZ 100 /* Internal kernel timer frequency */ # define USER_HZ 100 /* .. some user interfaces are in "ticks" */ # define CLOCKS_PER_SEC (USER_HZ) /* like times() */ #endif - 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/