[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 11 Oct 2012 04:52:16 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
stable <stable@...r.kernel.org>,
Ben Hutchings <ben@...adent.org.uk>,
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, Oct 10, 2012 at 03:24:03PM -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
Now applied to 3.4-stable queue.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists