public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Lundkvist <p.lundkvist@telia.com>
To: linux-kernel@vger.kernel.org
Subject: Bad interactive behaviour in 2.5.65-66 (sched.c)
Date: Sat, 29 Mar 2003 22:32:26 +0100	[thread overview]
Message-ID: <3E8610EA.8080309@telia.com> (raw)

Hi,

I have seen long delays when starting e.g. xterm from my
window manager (sawfish) either by keyboard-shortcut or by
menu command (by mouse) starting from 2.5.65. Sometimes it
starts immediately, sometimes after up to 2 seconds (idle
system). If I start a new xterm from xterm it always start
immediately. 2.5.64 always behaved OK.

My first try to solve this problem  was to use some
scheduler parameters from 2.6.64:
    #define MAX_TIMESLICE         (300 * HZ / 1000)
    #define CHILD_PENALTY         95
    #define MAX_SLEEP_AVG         (2*HZ)
    #define STARVATION_LIMIT      (2*HZ)

but got the same behaviour.

2nd try was to use sched.c, sched.h from 2.5.64 in a
2.5.66 build + one line patch in fork.c:
-       p->last_run = jiffies;
+       p->sleep_timestamp = jiffies;

Now the system behaves as it should!

My system is a P-III 700 (Inspiron 4000),
and Debian (X is running at nice = -10).

Best regards,
Peter Lundkvist


             reply	other threads:[~2003-03-29 21:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-29 21:32 Peter Lundkvist [this message]
2003-03-29 23:23 ` Bad interactive behaviour in 2.5.65-66 (sched.c) 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
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=3E8610EA.8080309@telia.com \
    --to=p.lundkvist@telia.com \
    --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