linux-kernel - Re: [RFC PATCH] sched: smart wake-affine

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: <1370228941.5988.66.camel@marge.simpson.net>
Date:	Mon, 03 Jun 2013 05:09:01 +0200
From:	Mike Galbraith <efault@....de>
To:	Michael Wang <wangyun@...ux.vnet.ibm.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Alex Shi <alex.shi@...el.com>,
	Namhyung Kim <namhyung@...nel.org>,
	Paul Turner <pjt@...gle.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Nikunj A. Dadhania" <nikunj@...ux.vnet.ibm.com>,
	Ram Pai <linuxram@...ibm.com>
Subject: Re: [RFC PATCH] sched: smart wake-affine

On Mon, 2013-06-03 at 10:28 +0800, Michael Wang wrote: 
> On 05/28/2013 01:05 PM, Michael Wang wrote:
> > wake-affine stuff is always trying to pull wakee close to waker, by theory,
> > this will bring benefit if waker's cpu cached hot data for wakee, or the
> > extreme ping-pong case.
> > 
> > And testing show it could benefit hackbench 15% at most.
> > 
> > However, the whole stuff is somewhat blindly and time-consuming, some
> > workload therefore suffer.
> > 
> > And testing show it could damage pgbench 50% at most.
> > 
> > Thus, wake-affine stuff should be smarter, and realise when to stop
> > it's thankless effort.
> 
> Is there any comments?

(I haven't had time to test-drive yet, -rt munches time like popcorn)

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