linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: Voluspa <voluspa@comhem.se>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Mike Galbraith <efault@gmx.de>, Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC] Re: Blender profiling-1 O16.2int
Date: Sun, 17 Aug 2003 17:30:05 -0700	[thread overview]
Message-ID: <20030818003005.GR32488@holomorphy.com> (raw)
In-Reply-To: <200308172336.42593.kernel@kolivas.org>

On Sun, Aug 17, 2003 at 11:36:42PM +1000, Con Kolivas wrote:
> Now for those that can't see what this is, blender and X are
> interactive tasks and getting high priority (PRI < 18) which makes
> sense. During heavy usage of blender, it is X that gets pegged for
> cpu usage (ie it is doing the work for blender), and eventually it
> gets expired onto the expired array for being naughty and stops doing
> anything till all other tasks have finished working on the active
> array. Now normally, blender should just sleep and wait till X comes
> alive again before it does anything. However here it shows clearly that 
> it is spinning madly looking for something from X, and poor X can't do 
> anything. This is the busy on wait I've described. Meanwhile, since blender 
> was seen as an interactive task (which it is), it preempts everything lower 
> priority than it till it also gets booted. 

Ugh, priority inversion.


-- wli

  parent reply	other threads:[~2003-08-18  0:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030817003128.04855aed.voluspa@comhem.se>
     [not found] ` <200308171142.33131.kernel@kolivas.org>
     [not found]   ` <20030817073859.51021571.voluspa@comhem.se>
2003-08-17 13:36     ` [RFC] Re: Blender profiling-1 O16.2int Con Kolivas
2003-08-17 16:34       ` Con Kolivas
2003-08-18  0:30       ` William Lee Irwin III [this message]
2003-08-19  0:14       ` Wes Janzen
2003-08-19  0:28         ` Con Kolivas
2003-08-19  0:37           ` Richard A Nelson
2003-08-19  8:39           ` Rob Landley
2003-08-19  0:31         ` William Lee Irwin III
2003-08-19  0:58         ` Wes Janzen
     [not found] <20030818110001.6564.64238.Mailman@lists.us.dell.com>
2003-08-18 12:52 ` Max Hailperin
2003-08-18 13:05   ` Con Kolivas
2003-08-18 14:43   ` William Lee Irwin III
2003-08-26  2:54 Kester Maddock
2003-08-26  5:03 ` 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=20030818003005.GR32488@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=akpm@osdl.org \
    --cc=efault@gmx.de \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=voluspa@comhem.se \
    /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).