From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261934AbVE0RkI (ORCPT ); Fri, 27 May 2005 13:40:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261900AbVE0Rj3 (ORCPT ); Fri, 27 May 2005 13:39:29 -0400 Received: from viper.oldcity.dca.net ([216.158.38.4]:50923 "HELO viper.oldcity.dca.net") by vger.kernel.org with SMTP id S261762AbVE0RjT (ORCPT ); Fri, 27 May 2005 13:39:19 -0400 Subject: Re: weird X problem - priority inversion? From: Lee Revell To: David Lang Cc: Ingo Molnar , linux-kernel In-Reply-To: References: <1113428938.16635.13.camel@mindpipe> <20050523075508.GC9287@elte.hu> <1117202510.13829.17.camel@mindpipe> Content-Type: text/plain Date: Fri, 27 May 2005 13:39:17 -0400 Message-Id: <1117215557.13829.76.camel@mindpipe> Mime-Version: 1.0 X-Mailer: Evolution 2.3.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2005-05-27 at 10:34 -0700, David Lang wrote: > On Fri, 27 May 2005, Lee Revell wrote: > > > On Mon, 2005-05-23 at 01:11 -0700, David Lang wrote: > >> remember that the low pri screensaver is just generating the image to be > >> displayed, it's the high pri X server that's actually doing the work to > >> display it. > > > > Then there needs to be some mechanism to handle it, either in X or the > > kernel. Other OSes do not require you to turn off the screensaver to > > avoid a DoS - they do the obvious thing and run the screensaver at the > > lowest priority. > > > > The problem may be software 3D rendering (I did not have the VIA driver > > enabled as I did not realize it was in the kernel yet). Maybe the X > > server should do the work in a low priority thread. But it sure > > shouldn't DoS the system. Other OSes do not have this problem. > > Actually they don't (or at least didn't the last time I took windows > training), if you have a CPU intensive screen saver on a windows server it > will seriously load down the box when it kicks in. That was a problem in the NT 4.0 days, but not lately. Lee