From: Lee Revell <rlrevell@joe-job.com>
To: Haoqiang Zheng <haoqiang@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] swap-sched: schedule with dynamic dependency detection (2.6.12-rc3)
Date: Sun, 08 May 2005 03:46:02 -0400 [thread overview]
Message-ID: <1115538362.19965.4.camel@mindpipe> (raw)
In-Reply-To: <d6e6e6dd050507231174d99fb0@mail.gmail.com>
On Sun, 2005-05-08 at 02:11 -0400, Haoqiang Zheng wrote:
> Certainly, this very problem can be solved by setting the priority of
> X to nice -10 (like what Redhat etc. does).
This just flips the priority inversion around: the nice -10 X server
will consume all available CPU rendering on behalf xscreensaver, running
at nice 20.
I would like to test this code very much, as this has been a real
problem for me.
Lee
next prev parent reply other threads:[~2005-05-08 7:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-08 6:11 [RFC PATCH] swap-sched: schedule with dynamic dependency detection (2.6.12-rc3) Haoqiang Zheng
2005-05-08 7:33 ` Con Kolivas
2005-05-08 15:55 ` Haoqiang Zheng
2005-05-08 23:26 ` Con Kolivas
2005-05-09 3:56 ` Haoqiang Zheng
2005-05-09 5:57 ` Con Kolivas
2005-05-11 4:23 ` Haoqiang Zheng
2005-05-08 7:46 ` Lee Revell [this message]
2005-05-10 8:22 ` Coywolf Qi Hunt
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=1115538362.19965.4.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=haoqiang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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