Hey, Viresh.
It's already too late for the upcoming merge window, but things
generally look good to me and I'll apply the patchset once wq/for-3.11
opens. One nitpick tho.
On Thu, Apr 25, 2013 at 09:13:44AM +0530, Viresh Kumar wrote:
> + workqueue.power_efficient
> + Workqueues can be performance or power-oriented.
> + Currently, most workqueues are bound to the CPU they
^^^^
per-cpu would be better
> + were created on. This gives good performance (due to
> + cache effects) at the cost of potentially waking up
> + otherwise idle cores just to process some work. To save
> + power, we can allow the work to be rescheduled on a core
> + that is already awake.
The above description is confusing to me. As have been discussed
multiple times before, per-cpu workqueue in itself doesn't wake up the
CPU physically. The timer may but per-cpu workqueue doesn't. It was
confusing when this patchset was first posted and the above phrasing
is still confusing. What the patchset tries to do is preventing the
scheduler from perceiving the CPU as active due to the activated
worker thread pinned to that CPU, right? The knob doesn't really do
anything about waking up the processor in itself. It just avoids
feeding the scheduler with noisy activation events and allows it to
allocate work item execution according to the scheduler's view of CPU
active/idleness. As the scheduler has longer / larger scope of
overall CPU activities and means to regulate them, this leads to more
power-efficient allocation of work item executions, right? It'd be
really great if the descriptions and the comment above the flag makes
this abundantly clear because it's not something too apparent.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
