linux-kernel - Re: 'autogroup' sched code KILLING responsiveness

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 23 Jan 2011 02:50:08 -0800 (PST)
From:	Christian Kujau <christian@...dbynature.de>
To:	Michael Witten <mfwitten@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: 'autogroup' sched code KILLING responsiveness

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.

Thanks,
Christian.
-- 
BOFH excuse #274:

It was OK before you touched it.
--
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/