From: Michael Witten <mfwitten@gmail.com>
To: Mike Galbraith <efault@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 'autogroup' sched code KILLING responsiveness
Date: Fri, 21 Jan 2011 16:39:03 -0600 [thread overview]
Message-ID: <AANLkTini15poUNM54UrM5KmGAoyJOznReYAFCkoxKEyN@mail.gmail.com> (raw)
In-Reply-To: <1295648870.23779.15.camel@marge.simson.net>
On Fri, Jan 21, 2011 at 16:27, Mike Galbraith <efault@gmx.de> wrote:
> On Fri, 2011-01-21 at 10:20 -0800, Michael Witten wrote:
>> Bisecting shows that this commit:
>>
>> 5091faa449ee0b7d73bc296a93bca9540fc51d0a
>> sched: Add 'autogroup' scheduling feature: automated per session task groups
>> Date: Tue Nov 30 14:18:03 2010 +0100
>>
>> is the reason that my computer has become unusable.
>>
>> 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).
>
> That's not what I'm experiencing with a UP kernel...
Before I try to gather any data, I'd like to point out that the
problem disappears when I disable CONFIG_SCHED_AUTOGROUP (General
setup -> Automatic process group scheduling).
Do you have it disabled?
next prev parent reply other threads:[~2011-01-21 22:39 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 [this message]
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 ` 'autogroup' sched code KILLING responsiveness Ingo Molnar
2011-01-23 15:53 ` 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=AANLkTini15poUNM54UrM5KmGAoyJOznReYAFCkoxKEyN@mail.gmail.com \
--to=mfwitten@gmail.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.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.