linux-kernel - Re: sched: tweak select_idle_sibling to look for idle threads

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: <1462784169.3803.146.camel@suse.de>
Date:	Mon, 09 May 2016 10:56:09 +0200
From:	Mike Galbraith <mgalbraith@...e.de>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Matt Fleming <matt@...eblueprint.co.uk>, Chris Mason <clm@...com>,
	Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: sched: tweak select_idle_sibling to look for idle threads

On Mon, 2016-05-09 at 10:33 +0200, Peter Zijlstra wrote:
> On Fri, May 06, 2016 at 08:54:38PM +0200, Mike Galbraith wrote:
> > master
> > Throughput 2722.43 MB/sec  4 clients  4 procs  max_latency=2.400 ms
> 
> > echo NO_IDLE_SIBLING > /sys/kernel/debug/sched_features
> > Throughput 3484.18 MB/sec  4 clients  4 procs  max_latency=3.430 ms
> 
> Yeah, I know about that bump, I just haven't managed to find a way to
> preserve that and keep all the other benchmarks ticking along :/

Yup, L3 ain't L2.  I haven't come up with a good metric either. Poo. 
 Until that comes along, microbenchmarks can bugger off, real boxen
don't just play high speed ping-pong with themselves for a living ;-)

	-Mike