mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Tom Sightler <ttsig@tuxyturvy.com>
Cc: rml@tech9.net, linux-kernel@vger.kernel.org
Subject: Re: Bad interactive behaviour in 2.5.65-66 (sched.c)
Date: Sat, 29 Mar 2003 21:23:30 -0800	[thread overview]
Message-ID: <20030329212330.225a96b6.akpm@digeo.com> (raw)
In-Reply-To: <1048996723.3058.41.camel@iso-8590-lx.zeusinc.com>

Tom Sightler <ttsig@tuxyturvy.com> wrote:
>
> On my system I get a starvation issue with just about any CPU intensive
> task.  For example if create a bzip'd tar file from the linux kernel
> source with the command:
> 
> tar cvp linux | bzip2 -9 > linux.tar.bz2
> 

Ingo has determined that Linus's backboost trick is causing at least some
of these problems. Please test and report upon the below patch.

I have another workload which is showing starvation with or without this
patch - it is the bitkeeper verification step in a `bk clone' on a
uniprocessor kernel.  Still poking at that one.






From: Ingo Molnar <mingo@elte.hu>

the patch below fixes George's setiathome problems (as expected).  It
essentially turns off Linus' improvement, but i dont think it can be fixed
sanely.

the problem with setiathome is that it displays something every now and
then - so it gets a backboost from X, and hovers at a relatively high
priority.



 kernel/sched.c |   13 +------------
 1 files changed, 1 insertion(+), 12 deletions(-)

diff -puN kernel/sched.c~sched-interactivity-backboost-revert kernel/sched.c
--- 25/kernel/sched.c~sched-interactivity-backboost-revert	2003-03-28 22:30:08.000000000 -0800
+++ 25-akpm/kernel/sched.c	2003-03-28 22:30:08.000000000 -0800
@@ -379,19 +379,8 @@ static inline int activate_task(task_t *
 		 * boosting tasks that are related to maximum-interactive
 		 * tasks.
 		 */
-		if (sleep_avg > MAX_SLEEP_AVG) {
-			if (!in_interrupt()) {
-				sleep_avg += current->sleep_avg - MAX_SLEEP_AVG;
-				if (sleep_avg > MAX_SLEEP_AVG)
-					sleep_avg = MAX_SLEEP_AVG;
-
-				if (current->sleep_avg != sleep_avg) {
-					current->sleep_avg = sleep_avg;
-					requeue_waker = 1;
-				}
-			}
+		if (sleep_avg > MAX_SLEEP_AVG)
 			sleep_avg = MAX_SLEEP_AVG;
-		}
 		if (p->sleep_avg != sleep_avg) {
 			p->sleep_avg = sleep_avg;
 			p->prio = effective_prio(p);

_


  reply	other threads:[~2003-03-30  5:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-29 21:32 Peter Lundkvist
2003-03-29 23:23 ` Robert Love
2003-03-30  1:21   ` Felipe Alfaro Solana
2003-03-30  2:05     ` Robert Love
2003-03-30  2:33       ` Con Kolivas
2003-03-30  2:46         ` Robert Love
2003-03-30  3:58           ` Tom Sightler
2003-03-30  5:23             ` Andrew Morton [this message]
2003-03-30 19:24               ` Tom Sightler
2003-04-01  1:41               ` Jeremy Fitzhardinge
2003-03-30 14:14           ` Jens Axboe
2003-03-30 21:06             ` Con Kolivas
2003-03-31  2:23               ` Mike Galbraith
2003-03-31  6:35                 ` Jens Axboe
2003-03-31  7:05                   ` Mike Galbraith
2003-03-31  8:46                     ` Felipe Alfaro Solana
2003-03-31  8:54                     ` Nick Piggin
2003-04-20  3:55                       ` Mike Galbraith
2003-04-18 13:58                   ` Mike Galbraith
2003-03-30 10:16       ` Felipe Alfaro Solana
2003-03-30 11:18   ` Mika Liljeberg

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=20030329212330.225a96b6.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    --cc=ttsig@tuxyturvy.com \
    /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

all inboxes | Powered by JetHome®