public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Christian Klose <christian.klose@freenet.de>,
	Marc-Christian Petersen <m.c.p@wolk-project.de>,
	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 14:37:57 +1000	[thread overview]
Message-ID: <200305251437.57464.kernel@kolivas.org> (raw)
In-Reply-To: <20030525042803.GA8978@holomorphy.com>

On Sun, 25 May 2003 14:28, William Lee Irwin III wrote:
> On Sun, May 25, 2003 at 11:27:20AM +1000, Con Kolivas wrote:
> > Even though you're not Marc I do agree with you. The problem is well
> > described as either poor interactivity (the window wiggle test) or
> > starvation in the presence of certain scheduler hogs (for whatever
> > reason) since the interactivity patch from mingo. Dropping the max
> > timeslice is a bandaid but destroys priority based timeslice
> > scheduling. Dropping the min timeslice will bring this back, but at
> > some point the timeslice will be so low that low priority cpu
> > intensive tasks will spend most of their time cache trashing.
>
> The fact that it's a "bandaid" and that it "destroys priority-based
> timeslice scheduling" makes it a shenanigan. If you're having problems

I don't disagree it's a shenanigan.

> solved by capping timeslices, you have someone's timeslice and/or
> priority growing too large for some reason.

So there is a benefit to timeslices being as large as 200ms? I'll take your 
word for it.

> It'd be far better to help figure out what went wrong.

Love to help. No idea where to begin. All we can do is report what helps the 
symptoms and hope those in the know can decipher it from that.

Con

      reply	other threads:[~2003-05-25  4:23 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
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 [this message]

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=200305251437.57464.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=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