From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>,
Ben Hutchings <ben@decadent.org.uk>,
Mike Galbraith <mgalbraith@suse.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: stable backport: sched: Fix migration thread runtime bogosity
Date: Thu, 11 Oct 2012 04:52:16 +0900 [thread overview]
Message-ID: <20121010195216.GA3928@kroah.com> (raw)
In-Reply-To: <1349897043.24256.63.camel@gandalf.local.home>
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@suse.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
next prev parent reply other threads:[~2012-10-10 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 19:24 stable backport: sched: Fix migration thread runtime bogosity Steven Rostedt
2012-10-10 19:52 ` Greg Kroah-Hartman [this message]
2012-10-14 9:27 ` Ben Hutchings
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=20121010195216.GA3928@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mgalbraith@suse.de \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.