From: Lee Revell <rlrevell@joe-job.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: weird X problem - priority inversion?
Date: Wed, 13 Apr 2005 17:48:58 -0400 [thread overview]
Message-ID: <1113428938.16635.13.camel@mindpipe> (raw)
I am having a problem with the RT preempt kernels where xscreensaver
will cause the X server to consume excessive CPU, starving other
processes. This should not happen as xscreensaver runs at the highest
nice value. It seems that there's some kind of priority inversion
happening between the high prio X server and low prio xscreensaver.
This seems like an X problem to me, but could the kernel be involved?
Lee
next reply other threads:[~2005-04-13 21:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 21:48 Lee Revell [this message]
2005-05-23 7:55 ` weird X problem - priority inversion? 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
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=1113428938.16635.13.camel@mindpipe \
--to=rlrevell@joe-job.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