From: Nick Piggin <piggin@cyberone.com.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Subject: Re: [PATCH] O13int for interactivity
Date: Tue, 05 Aug 2003 15:28:22 +1000 [thread overview]
Message-ID: <3F2F4076.1030009@cyberone.com.au> (raw)
In-Reply-To: <1060060568.3f2f3d989683f@kolivas.org>
Con Kolivas wrote:
>Quoting Nick Piggin <piggin@cyberone.com.au>:
>
snip
>
>>Oh, I'm not saying that your change is outright wrong, on the contrary I'd
>>say you have a better feel for what is needed than I do, but if you are
>>finding
>>that the uninterruptible sleep case needs some tweaking then the same tweak
>>should be applied to all sleep cases. If there really is a difference,
>>then its
>>just a fluke that the sleep paths in question use the type of sleep you are
>>testing for, and nothing more profound than that.
>>
>
>Ah I see. It was from my observations of the behaviour of tasks in D that
>found it was the period spent in D that was leading to unfairness. The same
>tweak can't be applied to the rest of the sleeps because that inactivates
>everything. So it is a fluke that the thing I'm trying to penalise is what
>tasks in uninterruptible sleep do, but it is by backward observation of D
>tasks, not random chance.
>
Yes yes, but we come to the same conclusion no matter why you have decided
to make the change ;) namely that you're only papering over a flaw in the
scheduler!
What happens in the same sort of workload that is using interruptible
sleeps?
Say the same make -j NFS mounted interrruptible (I think?).
I didn't really understand your answer a few emails ago... please just
reiterate: if the problem is that processes sleeping too long on IO get
too high a priority, then give all processes the same boost after they
have slept for half a second?
Also, why is this a problem exactly? Is there a difference between a
process that would be a CPU hog but for its limited disk bandwidth, and
a process that isn't a CPU hog? Disk IO aside, they are exactly the same
thing to the CPU scheduler, aren't they?
_wants_ to be a CPU hog, but can't due to disk
next prev parent reply other threads:[~2003-08-05 6:11 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 16:07 [PATCH] O13int for interactivity Con Kolivas
2003-08-04 18:24 ` Felipe Alfaro Solana
2003-08-04 19:15 ` Antonio Vargas
2003-08-04 21:32 ` Con Kolivas
2003-08-04 20:11 ` Mike Galbraith
2003-08-04 22:11 ` Con Kolivas
2003-08-05 7:10 ` Mike Galbraith
2003-08-05 2:11 ` Nick Piggin
2003-08-05 2:20 ` Con Kolivas
2003-08-05 2:21 ` Nick Piggin
2003-08-05 3:06 ` Con Kolivas
2003-08-05 3:17 ` Nick Piggin
2003-08-06 18:48 ` Interactivity improvements Timothy Miller
2003-08-06 19:01 ` Mike Fedyk
2003-08-06 20:09 ` Helge Hafting
2003-08-06 21:15 ` Con Kolivas
2003-08-05 3:18 ` [PATCH] O13int for interactivity Con Kolivas
2003-08-05 3:31 ` Nick Piggin
2003-08-05 5:04 ` Con Kolivas
2003-08-05 5:12 ` Nick Piggin
2003-08-05 5:16 ` Con Kolivas
2003-08-05 5:28 ` Nick Piggin [this message]
2003-08-05 10:22 ` Con Kolivas
2003-08-05 10:32 ` Nick Piggin
2003-08-05 10:45 ` Con Kolivas
2003-08-05 10:48 ` Nick Piggin
2003-08-05 10:56 ` Con Kolivas
2003-08-05 11:03 ` Nick Piggin
2003-08-05 11:12 ` Con Kolivas
2003-08-05 11:23 ` Nick Piggin
2003-08-05 11:34 ` Con Kolivas
2003-08-05 10:54 ` Arjan van de Ven
2003-08-05 11:10 ` Con Kolivas
2003-08-06 21:33 ` Timothy Miller
2003-08-06 21:33 ` Con Kolivas
2003-08-07 0:27 ` Timothy Miller
2003-08-07 0:27 ` Con Kolivas
2003-08-07 0:44 ` Timothy Miller
2003-08-11 6:48 ` Rob Landley
2003-08-11 15:47 ` William Lee Irwin III
2003-08-12 2:51 ` Nick Piggin
2003-08-12 6:16 ` Mike Galbraith
2003-08-12 7:07 ` Nick Piggin
2003-08-12 7:18 ` Nick Piggin
2003-08-12 9:42 ` Mike Galbraith
2003-08-12 21:11 ` Mike Fedyk
2003-08-13 6:55 ` Mike Galbraith
2003-08-12 9:22 ` Mike Galbraith
2003-08-12 9:37 ` Nick Piggin
2003-08-12 9:48 ` Mike Galbraith
2003-08-12 10:29 ` Rob Landley
2003-08-12 11:08 ` Nick Piggin
2003-08-12 11:35 ` Rob Landley
2003-08-12 11:58 ` Nick Piggin
2003-08-13 2:08 ` jw schultz
2003-08-13 3:07 ` Gene Heskett
2003-08-13 3:24 ` Nick Piggin
2003-08-13 5:24 ` Gene Heskett
2003-08-13 5:43 ` Andrew McGregor
2003-08-13 12:33 ` Gene Heskett
2003-08-14 5:03 ` Andrew McGregor
2003-08-14 10:48 ` Gene Heskett
2003-08-12 15:36 ` Timothy Miller
2003-08-05 6:03 ` Andrew Morton
2003-08-05 7:26 ` Con Kolivas
2003-08-05 8:12 ` Oliver Neukum
2003-08-05 8:20 ` Con Kolivas
2003-08-05 8:27 ` Mike Galbraith
2003-08-05 8:43 ` Con Kolivas
2003-08-05 9:09 ` Mike Galbraith
2003-08-05 9:19 ` Con Kolivas
2003-08-05 10:04 ` Nick Piggin
2003-08-11 6:57 ` Rob Landley
2003-08-11 15:58 ` William Lee Irwin III
2003-08-05 7:53 ` Mike Galbraith
[not found] <gQ4n.5oS.7@gated-at.bofh.it>
[not found] ` <jUl6.5eh.1@gated-at.bofh.it>
[not found] ` <jUuT.5kZ.15@gated-at.bofh.it>
[not found] ` <jWn1.6K1.11@gated-at.bofh.it>
2003-08-13 13:48 ` Pascal Schmidt
2003-08-13 14:50 ` Gene Heskett
-- strict thread matches above, loose matches on Subject: below --
2003-08-06 10:35 Voluspa
2003-08-04 19:12 Voluspa
2003-07-27 15:12 [PATCH] O10int " Con Kolivas
2003-07-28 18:08 ` Valdis.Kletnieks
2003-07-28 18:40 ` Andrew Morton
2003-08-04 18:51 ` [PATCH] O13int " Felipe Alfaro Solana
2003-08-04 18:58 ` Felipe Alfaro Solana
2003-08-04 21:46 ` Con Kolivas
2003-08-04 22:16 ` Felipe Alfaro Solana
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=3F2F4076.1030009@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=felipe_alfaro@linuxmail.org \
--cc=kernel@kolivas.org \
--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;
as well as URLs for NNTP newsgroup(s).