From: Christian Klose <christian.klose@freenet.de>
To: William Lee Irwin III <wli@holomorphy.com>,
Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: I/O problems in 2.4.19/2.4.20/2.4.21-rc3
Date: Sun, 25 May 2003 02:43:59 +0200 [thread overview]
Message-ID: <200305250242.58269.christian.klose@freenet.de> (raw)
In-Reply-To: <20030524142809.GZ8978@holomorphy.com>
On Saturday 24 May 2003 16:28, William Lee Irwin III wrote:
Hi wli,
> > --- old/kernel/sched.c 2003-05-24 14:45:57.000000000 +0200
> > +++ 2.5-mcp/kernel/sched.c 2003-05-24 16:18:42.000000000 +0200
> > @@ -65,7 +65,7 @@
> > * they expire.
> > */
> > #define MIN_TIMESLICE ( 10 * HZ / 1000)
> > -#define MAX_TIMESLICE (200 * HZ / 1000)
> > +#define MAX_TIMESLICE ( 10 * HZ / 1000)
> > #define CHILD_PENALTY 50
> > #define PARENT_PENALTY 100
> > #define EXIT_WEIGHT 3
> This looks highly suspicious as it essentially removes dynamic timeslice
> sizing. If this fixes something, then dynamic timeslice heuristics are
> going wrong somewhere that should be properly described and handled, not
> this kind of shenanigan.
I somewhat agree with you but this "properly described" are all the bug
reports on lkml containing "bad interactivity in 2.5, cpu starving in 2.5"
and such...
This isn't a shenanigan, at least not for the interactivity for a desktop.
This is a workaround for users who are complaining about bad interactivity in
2.5!
ciao, Marc
next prev parent reply other threads:[~2003-05-25 0:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 13:00 I/O problems in 2.4.19/2.4.20/2.4.21-rc3 Christian Klose
2003-05-23 13:46 ` Christian Klose
2003-05-23 14:35 ` Marc-Christian Petersen
2003-05-24 14:19 ` Marc-Christian Petersen
2003-05-24 14:28 ` William Lee Irwin III
2003-05-25 0:43 ` Christian Klose [this message]
2003-05-25 0:46 ` Marc-Christian Petersen
2003-05-25 1:27 ` Con Kolivas
2003-05-25 4:28 ` William Lee Irwin III
2003-05-25 4:37 ` 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=200305250242.58269.christian.klose@freenet.de \
--to=christian.klose@freenet.de \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--cc=wli@holomorphy.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;
as well as URLs for NNTP newsgroup(s).