All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathanael Hoyle <nhoyle@hoyletech.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: scheduler nice 19 versus 'idle' behavior / static low-priority scheduling
Date: Fri, 30 Jan 2009 04:00:30 -0500	[thread overview]
Message-ID: <1233306030.17301.36.camel@localhost> (raw)
In-Reply-To: <1233305433.4495.154.camel@laptop>

On Fri, 2009-01-30 at 09:50 +0100, Peter Zijlstra wrote:
> On Fri, 2009-01-30 at 00:49 -0500, Nathanael Hoyle wrote:
> > 
> > 1) Is my problem 'expected' based on others' understanding of the
> > current design of the scheduler, or do I have a one-off problem to
> > troubleshoot here?
> 
> What kernel are you running (or did my eye glance over that detail in
> your longish email) ?
> 

I didn't include it, I should have:

$ uname -a
Linux nightmare 2.6.27-gentoo-r7-nhoyle #2 SMP Wed Jan 28 19:04:37 EST
2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz GenuineIntel
GNU/Linux

> > 2) Am I overlooking obvious alternative (but clean) fixes?
> 
> Maybe, we fixed a glaring bug in this department recently (or more even,
> if you're on older than .28).
> 

Yep, .27 atm.

> > 3) Does anyone else see the need for static, but low process priorities?
> 
> Yep, its rather common.
> 
> > 4) What is the view of introducing a new scheduler class to handle this?
> 
> We should have plenty available, SCHED_IDLE should just work -- as
> should nice 19 for that matter.
> 

Thanks!
-Nathanael


  reply	other threads:[~2009-01-30  9:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30  5:49 scheduler nice 19 versus 'idle' behavior / static low-priority scheduling Nathanael Hoyle
2009-01-30  6:16 ` Jan Engelhardt
2009-01-30  6:40   ` Nathanael Hoyle
2009-01-30  7:21     ` Jan Engelhardt
2009-01-30  7:59       ` Nathanael Hoyle
2009-01-30  8:07         ` Mike Galbraith
2009-01-30  8:55           ` Nathanael Hoyle
2009-01-30  9:29             ` Mike Galbraith
2009-01-30 22:12           ` Brian Rogers
2009-01-31  5:38             ` Mike Galbraith
2009-01-31  9:08               ` Mike Galbraith
2009-02-02 23:57                 ` [stable] " Greg KH
2009-02-09 15:19                   ` Brian Rogers
2009-02-09 15:51                     ` Greg KH
2009-01-30  8:16         ` Nathanael Hoyle
2009-01-30 13:56           ` Jan Engelhardt
2009-01-30 14:15         ` Jan Engelhardt
2009-01-30  6:17 ` V.Radhakrishnan
2009-01-30  6:48   ` Nathanael Hoyle
2009-01-30 14:15     ` Jan Engelhardt
2009-01-30  6:24 ` Mike Galbraith
2009-01-30  6:52   ` Nathanael Hoyle
2009-01-30  7:09     ` Mike Galbraith
2009-01-30  8:50 ` Peter Zijlstra
2009-01-30  9:00   ` Nathanael Hoyle [this message]
2009-01-30  9:03     ` Peter Zijlstra
2009-01-30 10:18       ` Nathanael Hoyle
2009-01-30 10:31         ` Mike Galbraith
2009-01-30 10:40           ` Peter Zijlstra
2009-01-30 10:50             ` Mike Galbraith
2009-02-02 17:23 ` Lennart Sorensen

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=1233306030.17301.36.camel@localhost \
    --to=nhoyle@hoyletech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.