linux-kernel - [PATCH 0/2] cpufreq: governor: Optimize work queuing in ondemand/conservative

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

Date:	Fri, 12 Feb 2016 14:26:59 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Linux PM list <linux-pm@...r.kernel.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Viresh Kumar <viresh.kumar@...aro.org>,
	Juri Lelli <juri.lelli@....com>,
	Shilpasri G Bhat <shilpabhatppc@...il.com>
Subject: [PATCH 0/2] cpufreq: governor: Optimize work queuing in ondemand/conservative

Hi,

This is rather extreme, but I think that we should make the scheduler paths as
lightweight as reasonably possible.

[1/2] removes the atomic work counter incrementation from gov_cancel_work() as
      it is not necessary any more.

[2/2] changes the way work items are handled by dbs_update_util_handler() and
      dbs_work_handler() to avoid extra atomic operations in cases when they
      aren't really necessary (policy objects serving one CPU only).

On top of the pm-cpufreq-test branch of linux-pm.git.  Lightly tested, but
I don't have systems where policy objects are shared.

Thanks,
Rafael