public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Brian Rogers <brian@xyzw.org>
Cc: Nathanael Hoyle <nhoyle@hoyletech.com>,
	Jan Engelhardt <jengelh@medozas.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	stable <stable@kernel.org>
Subject: Re: scheduler nice 19 versus 'idle' behavior / static low-priority scheduling
Date: Sat, 31 Jan 2009 06:38:04 +0100	[thread overview]
Message-ID: <1233380284.5636.5.camel@marge.simson.net> (raw)
In-Reply-To: <49837B32.3010206@xyzw.org>

On Fri, 2009-01-30 at 14:12 -0800, Brian Rogers wrote:
> Mike Galbraith wrote:
> > On Fri, 2009-01-30 at 02:59 -0500, Nathanael Hoyle wrote:
> >   
> >> I am running foldingathome under it at the moment, and it seems to be
> >> improving the situation somewhat, but I still need/want to test with
> >> Mike's referenced patches.
> >>     
> > You will most definitely encounter evilness running SCHED_IDLE tasks in
> > a kernel without the SCHED_IDLE fixes.
> >   
> Speaking of SCHED_IDLE fixes, is 
> 6bc912b71b6f33b041cfde93ca3f019cbaa852bc going to be put into the next 
> stable 2.6.28 release? Without it on 2.6.28.2, I can still produce 
> minutes-long freezes with BOINC or other idle processes.
> 
> With the above commit on top of 2.6.28.2 and also 
> cce7ade803699463ecc62a065ca522004f7ccb3d, the problem is solved, though 
> I assume cce7ad isn't actually required to fix that, and I can test that 
> if desired.

I think they both should go to stable, but dunno if they're headed that
direction or not.

One way to find out, CCs added.

	-Mike


  reply	other threads:[~2009-01-31  5:38 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 [this message]
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
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=1233380284.5636.5.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=brian@xyzw.org \
    --cc=jengelh@medozas.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nhoyle@hoyletech.com \
    --cc=stable@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox