linux-kernel - Re: [RFC PATCH] sched: Pass affine target cpu into wake

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

Message-Id: <1262921669.5601.25.camel@marge.simson.net>
Date:	Fri, 08 Jan 2010 04:34:29 +0100
From:	Mike Galbraith <efault@....de>
To:	Lin Ming <ming.m.lin@...el.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	lkml <linux-kernel@...r.kernel.org>,
	"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>
Subject: Re: [RFC PATCH] sched: Pass affine target cpu into wake_affine

On Fri, 2010-01-08 at 10:38 +0800, Lin Ming wrote:
> On Thu, 2010-01-07 at 21:14 +0800, Mike Galbraith wrote:

> > Below is a complete retest.  Mind testing my hacklet?  I bet a nickle
> > it'll work at least as well as yours on your beefy boxen.
> 
> I tested your hacklet on below 2 machines as before.
> 
> Tigerton x86_64 machine: 16cpus(4P/4Cores), 40G mem
> IA64 machine: 32cpus(4P/4Cores/HT), 16G mem
> 
> Test1: vmark regression fix patch + pass affine target
> Test2: this hacklet
> 
> Compared with upstream 2.6.33-rc2, 
> Test1: Tigerton +3%, IA64 +15%
> Test2: Tigerton +3%, IA64 +10%
> 
> The test2 also improves on IA64, although not as good as test1.

Dang, I owe you a nickle.  Thanks a bunch for giving it a go.

Interesting result.  It's not really making much sense why you see a
peak gain, while I see peak loss.  Radical behavior difference :-/

I think the ramp only (and harder) approach is safer, but we'll see.

	-Mike

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