From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Nick Piggin <piggin@cyberone.com.au>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Nick's scheduler policy v12
Date: Fri, 05 Sep 2003 13:19:24 -0700 [thread overview]
Message-ID: <207340000.1062793164@flay> (raw)
In-Reply-To: <20030905202232.GD19041@matchmail.com>
> On Fri, Sep 05, 2003 at 11:54:04AM -0700, Martin J. Bligh wrote:
>> > Backboost is gone so X really should be at -10 or even higher.
>>
>> Wasn't that causing half the problems originally? Boosting X seemed
>> to starve xmms et al. Or do the interactivity changes fix xmms
>> somehow, but not X itself? Explicitly fiddling with task's priorities
>> seems flawed to me.
>
> Wasn't it the larger timeslices with lower nice values in stock and Con's
> patches that made X with nice -10 a bad idea?
Debian renices X by default to -10 ... I fixed all my desktop interactivity
problems around 2.5.63 timeframe by just turning that off. That was way
before Con's patches.
There may be some more details around this, and I'd love to hear them,
but I fundmantally believe that explitit fiddling with particular
processes because we believe they're somehow magic is wrong (and so
does Linus, from previous discussions).
M.
next prev parent reply other threads:[~2003-09-05 20:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 17:57 [PATCH] Nick's scheduler policy v12 Nick Piggin
2003-09-05 18:54 ` Martin J. Bligh
2003-09-05 20:22 ` Mike Fedyk
2003-09-05 20:19 ` Martin J. Bligh [this message]
2003-09-05 20:39 ` Mike Fedyk
2003-09-05 21:08 ` Robert Love
2003-09-06 1:31 ` Nick Piggin
2003-09-06 1:18 ` Nick Piggin
2003-09-06 3:36 ` Martin J. Bligh
2003-09-06 6:20 ` Jörn Engel
2003-09-06 6:38 ` Nick Piggin
2003-09-06 6:55 ` Nick Piggin
2003-09-06 15:13 ` Martin J. Bligh
2003-09-06 11:47 ` Ed Sweetman
2003-09-07 2:34 ` Martin J. Bligh
2003-09-07 3:27 ` Valdis.Kletnieks
2003-09-07 4:42 ` Nick Piggin
2003-09-07 4:37 ` Nick Piggin
2003-09-06 7:49 ` Martin Schlemmer
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=207340000.1062793164@flay \
--to=mbligh@aracnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
--cc=piggin@cyberone.com.au \
/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