linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Mike Galbraith <efault@gmx.de>
Cc: hzheng@cs.columbia.edu, Nick Piggin <piggin@cyberone.com.au>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [CFT][PATCH] new scheduler policy
Date: Tue, 19 Aug 2003 19:13:51 -0700	[thread overview]
Message-ID: <20030820021351.GE4306@holomorphy.com> (raw)
In-Reply-To: <5.2.1.1.2.20030819113225.019dae48@pop.gmx.net>

On Tue, Aug 19, 2003 at 12:24:17PM +0200, Mike Galbraith wrote:
> Test-starve.c starvation is back (curable via other means), but irman2 is 
> utterly harmless.  Responsiveness under load is very nice until I get to 
> the "very hefty" end of the spectrum (expected).  Throughput is down a bit 
> at make -j30, and there are many cc1's running at very high priority once 
> swap becomes moderately busy.  OTOH, concurrency for the make -jN in 
> general appears to be up a bit.  X is pretty choppy when moving windows 
> around, but that _appears_ to be the newer/tamer backboost bleeding a 
> kdeinit thread a bit too dry.  (I think it'll be easy to correct, will let 
> you know if what I have in mind to test that theory works out).  Ending on 
> a decidedly positive note, I can no longer reproduce priority inversion 
> troubles with xmms's gl thread, nor with blender.
> (/me wonders what the reports from wine/game folks will be like)

Someone else appears to have done some work on the X priority inversion
issue who I'd like to drag into this discussion, though there doesn't
really appear to be an opportune time.

Haoqiang, any chance you could describe your solutions to the X priority
inversion issue?


-- wli

  parent reply	other threads:[~2003-08-20  2:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19  1:53 [CFT][PATCH] new scheduler policy Nick Piggin
2003-08-19  2:35 ` William Lee Irwin III
2003-08-19  2:46   ` Nick Piggin
2003-08-19  2:59     ` Nick Piggin
2003-08-19  5:15       ` Matt Mackall
2003-08-19  5:34         ` Nick Piggin
2003-08-19  5:45           ` Matt Mackall
2003-08-19 10:24 ` Mike Galbraith
2003-08-19 13:40   ` Nick Piggin
2003-08-19 18:49     ` Mike Galbraith
2003-08-20  2:13   ` William Lee Irwin III [this message]
2003-08-25 13:47     ` Haoqiang Zheng
2003-08-25 14:03       ` Nick Piggin
2003-08-25 15:11         ` Haoqiang Zheng
2003-09-02 14:25           ` Pavel Machek
2003-09-08 13:40             ` Alan Cox
2003-09-08 14:20               ` Haoqiang Zheng
2003-09-08 14:28                 ` Alan Cox
2003-09-08 15:10                   ` Haoqiang Zheng
2003-08-22  8:55 ` Roger Luethi
2003-08-22 13:08   ` Nick Piggin
2003-08-22 15:11     ` Roger Luethi
2003-08-23  0:22       ` Nick Piggin

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=20030820021351.GE4306@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=efault@gmx.de \
    --cc=hzheng@cs.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    /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).