All of lore.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: "Szonyi Calin" <sony@etc.utt.ro>, <felipe_alfaro@linuxmail.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] O8int for interactivity
Date: Fri, 25 Jul 2003 08:20:49 +1000	[thread overview]
Message-ID: <200307250820.49434.kernel@kolivas.org> (raw)
In-Reply-To: <5783.194.138.39.55.1059063130.squirrel@webmail.etc.utt.ro>

On Fri, 25 Jul 2003 02:12, Szonyi Calin wrote:
> Felipe Alfaro Solana said:
> > I'm playing a bit with tunables to see if I can tune the scheduler a
> > little bit for my system/workload. I've had good results reducing max
> > timeslice to 100 (yeah, I know I shouldn't do this too).
> >
> > Will keep you informed :-)
>
> same thing here. Reducing max timeslice to 100 is much better.
> It's the only thing that allow me to watch a movie while compiling
> the kernel with make -j 2 bzImage on my Duron 700Mhz with 256M RAM

Does this patch help?

Con

--- linux-2.6.0-test1-mm2/kernel/sched.c	2003-07-24 10:31:41.000000000 +1000
+++ linux-2.6.0-test1ck2/kernel/sched.c	2003-07-25 08:18:54.000000000 +1000
@@ -1243,7 +1243,7 @@ void scheduler_tick(int user_ticks, int 
 		} else
 			enqueue_task(p, rq->active);
 	} else if (p->mm && !((task_timeslice(p) - p->time_slice) %
-		 (MIN_TIMESLICE * (MAX_BONUS + 1 - p->sleep_avg * MAX_BONUS / MAX_SLEEP_AVG)))){
+		 (MIN_TIMESLICE * (1 + (MAX_BONUS - p->sleep_avg * MAX_BONUS / MAX_SLEEP_AVG) / 2)))){
 		/*
 		 * Running user tasks get requeued with their remaining timeslice
 		 * after a period proportional to how cpu intensive they are to


  reply	other threads:[~2003-07-24 22:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 11:55 [PATCH] O8int for interactivity Con Kolivas
2003-07-23 16:46 ` Felipe Alfaro Solana
2003-07-24 16:12   ` Szonyi Calin
2003-07-24 22:20     ` Con Kolivas [this message]
2003-07-26  9:03   ` Eugene Teo

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=200307250820.49434.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=felipe_alfaro@linuxmail.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sony@etc.utt.ro \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.