From: Nick Piggin <piggin@cyberone.com.au>
To: Kurt Garloff <garloff@suse.de>
Cc: Con Kolivas <kernel@kolivas.org>,
Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: bonus inheritance
Date: Tue, 16 Mar 2004 16:54:49 +1100 [thread overview]
Message-ID: <405696A9.3060304@cyberone.com.au> (raw)
In-Reply-To: <20040315225459.GY4452@tpkurt.garloff.de>
Kurt Garloff wrote:
>
>The patch was written with the goal to improve interactive behaviour.
>It did achieve this. Processes freshly started had a higher bonus thatn
>the background kernel compile processes and thus get woken up.
>
>
Hi Kurt,
I'm sorry I can't comment too much on your patch, as I am not
too familiar with 2.6's scheduler policy. Never hurts to have
another pair of eyes looking at it though.
Does it help any actual interactivity problem? Unfortunately
practically any you make to the scheduler is bound to make
things worse for at least one person, so it is difficult to
just test things out.
Maybe we could include a compile (or even boot) time selectable
schedulers to test improvements. Or wait for 2.7 and backport
good bits. These two options still have the problem that most
of the users that matter still won't test them...
That said, if you have any real, reproducable problems that it
solves, you far improve your chances of it being picked up (in
one form or another).
Nick
next prev parent reply other threads:[~2004-03-16 5:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 22:54 bonus inheritance Kurt Garloff
2004-03-15 23:31 ` Con Kolivas
2004-03-16 5:54 ` Nick Piggin [this message]
2004-03-16 11:48 ` Kurt Garloff
2004-03-16 12:21 ` Con Kolivas
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=405696A9.3060304@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=garloff@suse.de \
--cc=kernel@kolivas.org \
--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