public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: David Lang <dlang@digitalinsight.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: weird X problem - priority inversion?
Date: Fri, 27 May 2005 13:39:17 -0400	[thread overview]
Message-ID: <1117215557.13829.76.camel@mindpipe> (raw)
In-Reply-To: <Pine.LNX.4.62.0505271034010.14917@qynat.qvtvafvgr.pbz>

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


  reply	other threads:[~2005-05-27 17:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13 21:48 weird X problem - priority inversion? Lee Revell
2005-05-23  7:55 ` Ingo Molnar
2005-05-23  8:08   ` Serge Noiraud
2005-05-23  8:11   ` David Lang
2005-05-27 13:51     ` Lee Revell
2005-05-27 14:01     ` Lee Revell
2005-05-27 17:34       ` David Lang
2005-05-27 17:39         ` Lee Revell [this message]
2005-05-27 17:48           ` David Lang
2005-05-27 14:03   ` Lee Revell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1117215557.13829.76.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=dlang@digitalinsight.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox