linux-kernel - Re: [PATCH 2/2] sched: Improve fairness of cpu allocation for task groups

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: <20071119131201.GB31491@elte.hu>
Date:	Mon, 19 Nov 2007 14:12:01 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>
Cc:	dmitry.adamushko@...il.com, a.p.zijlstra@...llo.nl,
	dhaval@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
	efault@....de, skumar@...ux.vnet.ibm.com,
	Balbir Singh <balbir@...ibm.com>
Subject: Re: [PATCH 2/2] sched: Improve fairness of cpu allocation for task
	groups

* Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com> wrote:

> The current load balancing scheme isn't good for group fairness.

> ---
>  include/linux/sched.h |    4 
>  kernel/sched.c        |  292 +++++++++++++++++++++++++++++++++++++++++++++-----
>  kernel/sched_fair.c   |   95 ++++++++++------
>  kernel/sched_rt.c     |    2 
>  kernel/sysctl.c       |   16 ++
>  5 files changed, 348 insertions(+), 61 deletions(-)

i'm leaning towards making this v2.6.25 material, as it affects the 
non-group-scheduling bits too and is rather large. When i tested it, 
group scheduling worked pretty well - at least for CPU bound tasks - and 
on SMP too. Could we live with what we have for now and defer this patch 
to v2.6.25? If not, could you split up this patch in a way to defer all 
the FAIR_GROUP_SCHED relevant changes to a separate patch which will not 
affect the !FAIR_GROUP_SCHED case at all? That will make the case much 
clearer.

	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/