linux-kernel - Re: [RFC][PATCH 4/7] sched: power: Remove power capacity hints for kworker 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131014133356.GN3081@twins.programming.kicks-ass.net>
Date:	Mon, 14 Oct 2013 15:33:56 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Morten Rasmussen <morten.rasmussen@....com>
Cc:	mingo@...nel.org, pjt@...gle.com, arjan@...ux.intel.com,
	rjw@...k.pl, dirk.j.brandewie@...el.com,
	vincent.guittot@...aro.org, alex.shi@...aro.org,
	preeti@...ux.vnet.ibm.com, efault@....de, corbet@....net,
	tglx@...utronix.de, catalin.marinas@....com,
	linux-kernel@...r.kernel.org, linaro-kernel@...ts.linaro.org
Subject: Re: [RFC][PATCH 4/7] sched: power: Remove power capacity hints for
 kworker threads

On Fri, Oct 11, 2013 at 06:19:14PM +0100, Morten Rasmussen wrote:
> Removing power hints for kworker threads enables easier use of
> workqueues in the power driver late callback. That would otherwise
> lead to an endless loop unless it is prevented in the power driver.

There's many kworker users; some of them actually consume lots of
cputime. Therefore how did you come to the conclusion that excepting all
users was the better choice of a little added complexity in the one
place where it actually matters?
--
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/