From: Mike Galbraith <efault@gmx.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Nathanael Hoyle <nhoyle@hoyletech.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable <stable@kernel.org>
Subject: Re: scheduler nice 19 versus 'idle' behavior / static low-priority scheduling
Date: Fri, 30 Jan 2009 11:50:57 +0100 [thread overview]
Message-ID: <1233312657.6769.3.camel@marge.simson.net> (raw)
In-Reply-To: <1233312042.4495.167.camel@laptop>
On Fri, 2009-01-30 at 11:40 +0100, Peter Zijlstra wrote:
> On Fri, 2009-01-30 at 11:31 +0100, Mike Galbraith wrote:
> > On Fri, 2009-01-30 at 05:18 -0500, Nathanael Hoyle wrote:
> >
> > > Ok, I'm now running:
> > >
> > > Linux nightmare 2.6.28.2-nhoyle #1 SMP Fri Jan 30 04:50:03 EST 2009
> > > x86_64 Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz GenuineIntel
> > > GNU/Linux
> > >
> > > Initial conclusion is that whatever defects were corrected (non
> > > SCHED_IDLE specific defects that is), the newer kernel version does the
> > > trick. Video playback is as smooth as ever when running foldingathome
> > > at simple nice 19 priority.
> >
> > Good to hear, thanks for testing.
> >
> > Peter, since 27 is a long term maintenance kernel, do you think 1af5f73
> > and 046e7f7 (at least) are 27.stable candidates?
>
> 1af5f730fc1bf7c62ec9fb2d307206e18bf40a69 and
> e17036dac189dd034c092a91df56aa740db7146d you mean?
Yeah.
> I guess that makes sense.
(adds cc)
-Mike
next prev parent reply other threads:[~2009-01-30 10:51 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
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 [this message]
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=1233312657.6769.3.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nhoyle@hoyletech.com \
--cc=peterz@infradead.org \
--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 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.