linux-kernel - Re: [Patch 0/5] sched: group scheduler related patches (V4)

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: <20071127110910.GB16273@elte.hu>
Date:	Tue, 27 Nov 2007 12:09:10 +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>,
	Dipankar <dipankar@...ibm.com>
Subject: Re: [Patch 0/5] sched: group scheduler related patches (V4)


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

> On Mon, Nov 26, 2007 at 09:28:36PM +0100, Ingo Molnar wrote:
> > the first SCHED_RR priority is 1, not 0 - so this call will always fail.
> 
> Thanks for spotting this bug and rest of your review comments.
> 
> Here's V4 of the patchset, aimed at improving fairness of cpu 
> bandwidth allocation for task groups.

thanks, it looks good - but the fact that we are at v4 of the patchset 
underlines the point that this is more of a v2.6.25 patchset than a 
v2.6.24 one. Group fairness certainly works fine enough in most setups 
and we are late into the v2.6.24 -rc stage. We'll merge this patchset 
(or any later versions of it) into v2.6.25 for sure, so distros that 
happen to base things off v2.6.24 can pick up your patches just fine.

	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/