linux-kernel - Re: How to disable group scheduler correctly?

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]

Message-ID: <488DF70E.20404@nortel.com>
Date:	Mon, 28 Jul 2008 10:42:54 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	luis6674@...oo.com
CC:	linux-kernel@...r.kernel.org
Subject: Re: How to disable group scheduler correctly?

Alberto Gonzalez wrote:

> [1] For example, in Arch Linux the group scheduler was first enabled
> in 2.6.25, but due to latency issues it was quickly disabled. But
> after that, the following report claims to have problems with
> everything *GROUP* disabled and that you need to enable CGROUPS to
> solve them (the report links to similar reports on Gentoo and Ubuntu,
> so it seems the confusion is quite general):
> 
> http://bugs.archlinux.org/task/10512

The linked thread talks about latency problems in the CFQ I/O scheduler, 
not the process scheduler.  It appears that enabling CGROUPS helps get 
around the I/O scheduler issues.

Are you sure that you actually want to disable group scheduling for 
processes?

Chris
--
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/