public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Yong Zhang <yong.zhang0@gmail.com>
Cc: Christian Kujau <christian@nerdbynature.de>,
	Michael Witten <mfwitten@gmail.com>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Mike Galbraith <efault@gmx.de>
Subject: Re: 'autogroup' sched code KILLING responsiveness
Date: Sun, 23 Jan 2011 16:15:56 +0100	[thread overview]
Message-ID: <20110123151556.GA15236@elte.hu> (raw)
In-Reply-To: <20110123145429.GA2523@zhy>


* Yong Zhang <yong.zhang0@gmail.com> wrote:

> On Sun, Jan 23, 2011 at 02:50:08AM -0800, Christian Kujau wrote:
> > On Fri, 21 Jan 2011 at 10:20, Michael Witten wrote:
> > > With that code in place, a resource-intensive activity (such as
> > > compiling the Linux kernel) causes my computer to become
> > > unresponsive for many seconds at a time; the entire screen
> > > does not refresh, typed keys are dropped or are handled very
> > > late, etc (even in Linux's plain virtual consoles).
> > 
> > Unfortunately, I'd like to add a "me too". 2.6.38-rc1 behaves fine, but 
> > with CONFIG_SCHED_AUTOGROUP=y and doing I/O and CPU intensive work (git 
> > prune/git repack on a Linux git tree), system load goes up to ~13 and 
> > becomes unresponse for some time too. This even happens when I start the 
> > jobs with nice -n10.
> > 
> > Without CONFIG_SCHED_AUTOGROUP enabled and doing the same work,
> > systemload goes up to 1 or maybe 2.
> > 
> > I'm on UP as well (PowerPC G4), disabling CONFIG_SCHED_AUTOGROUP helps 
> > here too.
> 
> I think below patch will fix it.

Christian, Michael, can you confirm that this and the second patch fixes the 
interactivity bug for you? If yes then i'd like to apply and send this fix to Linus 
ASAP.

Thanks,

	Ingo

  parent reply	other threads:[~2011-01-23 15:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 18:20 'autogroup' sched code KILLING responsiveness Michael Witten
2011-01-21 22:27 ` Mike Galbraith
2011-01-21 22:39   ` Michael Witten
2011-01-22  3:22     ` Mike Galbraith
2011-01-22 21:23   ` Michael Witten
2011-01-23  3:32     ` Michael Witten
2011-01-23  5:42       ` Mike Galbraith
2011-01-23 10:50 ` Christian Kujau
2011-01-23 11:19   ` Christian Kujau
2011-01-23 14:54   ` Yong Zhang
2011-01-23 15:03     ` [PATCH] sched: fix autogroup nice tune on UP Yong Zhang
2011-01-23 15:16       ` Pekka Enberg
2011-01-24  3:17         ` Yong Zhang
2011-01-24  5:40       ` [PATCH V2] " Yong Zhang
2011-01-24  5:54         ` Pekka Enberg
2011-01-24  6:11           ` Yong Zhang
2011-01-24  6:18             ` Pekka Enberg
2011-01-24  7:33               ` [PATCH V3] " Yong Zhang
2011-01-24  8:01                 ` Pekka Enberg
2011-01-24  9:00                 ` Mike Galbraith
2011-01-24 10:51                 ` [tip:sched/urgent] sched: Fix poor interactivity on UP systems due to group scheduler nice tune bug tip-bot for Yong Zhang
2011-01-23 15:15     ` Ingo Molnar [this message]
2011-01-23 15:53       ` 'autogroup' sched code KILLING responsiveness Michael Witten
2011-01-23 18:52       ` Andreas Mohr
2011-01-23 23:57       ` Christian Kujau

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=20110123151556.GA15236@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=christian@nerdbynature.de \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfwitten@gmail.com \
    --cc=yong.zhang0@gmail.com \
    /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