From: Martin Schlemmer <azarah@gentoo.org>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Nick Piggin <piggin@cyberone.com.au>,
Mike Fedyk <mfedyk@matchmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Nick's scheduler policy v12
Date: Sat, 06 Sep 2003 09:49:19 +0200 [thread overview]
Message-ID: <1062834559.3372.35.camel@workshop.saharacpt.lan> (raw)
In-Reply-To: <6470000.1062819391@[10.10.2.4]>
On Sat, 2003-09-06 at 05:36, Martin J. Bligh wrote:
> > Well it would be nice if someone could find out how to do it, but I
> > think that if we want X to be able to get 80% CPU when 2 other CPU hogs
> > are running, you have to renice it.
>
> OK. So you renice it ... then your two cpu jobs exit, and you kick off
> xmms. Every time you waggle a window, X will steal the cpu back from
> xmms, and it'll stall, surely? That's what seemed to happen before.
> I don't see how you can fix anything by doing static priority alterations
> (eg nice), because the workload changes.
>
Not here with version 10 of Nick's patch, and X reniced to -10.
I have not had chance to test v12, but will do tonight when I
get home.
Cheers,
--
Martin Schlemmer
prev parent reply other threads:[~2003-09-06 7:59 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
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 [this message]
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=1062834559.3372.35.camel@workshop.saharacpt.lan \
--to=azarah@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--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