linux-kernel - Re: [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8, v2.6.21.7, v2.6.20.20

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>] [day] [month] [year] [list]

Date:	Sun, 30 Sep 2007 19:27:36 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Matthew <jackdachef@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8,
	v2.6.22.8, v2.6.21.7, v2.6.20.20

* Matthew <jackdachef@...il.com> wrote:

> Thanks for your answer (sorry, I didn't know your email had changed)
> 
> well, this will take some time since I don't work every day & it's 
> turned off most of the time, hope that is OK
> 
> before I proceed with that data-collection:
> 
> do you think it is possible that it might be related to "Fair group 
> CPU scheduler" being selected ?

i think if you are relatively sure that the box does not have any real 
3D hardware in it (supported by X) then glxgears will interact badly 
with X and can cause such symptoms. In that case glxgears 'spams' the X 
server with requests and everyone else suffers from that. The fair-group 
scheduler indeed could shift CPU usage of X just enough (in X's favor!) 
that might trigger such problems. Such "spam X" workloads often react in 
a paradoxial way: a scheduler that gives X _more_ CPU time will appear 
to be "less interactive".)

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