mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [PATCH 0/2] cpufreq: governor: Optimize work queuing in ondemand/conservative
@ 2016-02-12 13:26 Rafael J. Wysocki
  2016-02-12 13:28 ` [PATCH 1/2] cpufreq: governor: Simplify gov_cancel_work() slightly Rafael J. Wysocki
  2016-02-12 13:33 ` [PATCH 2/2] cpufreq: governor: Avoid atomic operations in hot paths Rafael J. Wysocki
  0 siblings, 2 replies; 3+ messages in thread
From: Rafael J. Wysocki @ 2016-02-12 13:26 UTC (permalink / raw)
  To: Linux PM list
  Cc: Linux Kernel Mailing List, Viresh Kumar, Juri Lelli, Shilpasri G Bhat

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-02-12 13:33 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-02-12 13:26 [PATCH 0/2] cpufreq: governor: Optimize work queuing in ondemand/conservative Rafael J. Wysocki
2016-02-12 13:28 ` [PATCH 1/2] cpufreq: governor: Simplify gov_cancel_work() slightly Rafael J. Wysocki
2016-02-12 13:33 ` [PATCH 2/2] cpufreq: governor: Avoid atomic operations in hot paths Rafael J. Wysocki

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®