linux-kernel - [test] sched: SD-latest versus Mike's latest

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:	Thu, 5 Apr 2007 13:54:47 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Mike Galbraith <efault@....de>
Cc:	Con Kolivas <kernel@...ivas.org>,
	linux list <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	ck list <ck@....kolivas.org>
Subject: [test] sched: SD-latest versus Mike's latest


* Mike Galbraith <efault@....de> wrote:

> On Tue, 2007-04-03 at 08:01 +0200, Ingo Molnar wrote:
> 
> > looks interesting - could you send the patch?
> 
> Ok, this is looking/feeling pretty good in testing.  Comments on 
> fugliness etc much appreciated.
>
> Below the numbers is a snapshot of my experimental tree.  It's a 
> mixture of my old throttling/anti-starvation tree and the task 
> promotion patch, with the addition of a scheduling class for 
> interactive tasks to dish out some of that targeted unfairness I 
> mentioned.

here's some test results, comparing SD-latest to Mike's-latest:

re-testing the weak points of the vanilla scheduler + Mike's:

 - thud.c:    this workload has almost unnoticeable effect
 - fiftyp.c:  noticeable, but alot better than previously!

re-testing the weak points of SD:

 - hackbench: still unusable under such type of high load - no improvement.
 - make -j:   still less interactive than Mike's - no improvement.

	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/