[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1350206827.4832.74.camel@deadeye.wl.decadent.org.uk>
Date: Sun, 14 Oct 2012 10:27:07 +0100
From: Ben Hutchings <ben@...adent.org.uk>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
stable <stable@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Mike Galbraith <mgalbraith@...e.de>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: stable backport: sched: Fix migration thread runtime bogosity
On Wed, 2012-10-10 at 15:24 -0400, Steven Rostedt wrote:
> Greg, Ben,
>
> Can you add this commit to the stable branches. Without it, the
> migration thread's accounting is just totally screwed up:
>
> By running a simple shell while loop along with a ps loop, top shows:
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 17 root RT 0 0 0 0 S 9999.0 0.0 9:27.50 migration/3
> 13 root RT 0 0 0 0 S 128.2 0.0 9:50.23 migration/2
> 2805 root 20 0 105m 1904 1416 S 13.9 0.1 0:06.69 bash
> 4090 root 20 0 105m 1904 1416 S 2.0 0.1 0:00.90 bash
> 2773 root 20 0 85484 3372 2620 S 0.3 0.2 0:00.03 sshd
>
>
> For 3.4, the commit can be directly cherry picked:
>
> commit 8f6189684eb4e85e6c593cd710693f09c944450a
> Author: Mike Galbraith <mgalbraith@...e.de>
> Date: Sat Aug 4 05:44:14 2012 +0200
>
> sched: Fix migration thread runtime bogosity
>
> Below is a backport for 3.2.
[...]
Queued up for 3.2, thanks.
Ben.
--
Ben Hutchings
Always try to do things in chronological order;
it's less confusing that way.
Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)
Powered by blists - more mailing lists