>From cee22a15052faa817e3ec8985a28154d3fabc7aa Mon Sep 17 00:00:00 2001
From: Viresh Kumar
Date: Mon, 8 Apr 2013 16:45:40 +0530
Subject: workqueues: Introduce new flag WQ_POWER_EFFICIENT for power oriented
workqueues
Workqueues can be performance or power-oriented. Currently, most workqueues
From cee22a15052faa817e3ec8985a28154d3fabc7aa Mon Sep 17 00:00:00 2001
From: Viresh Kumar viresh.ku...@linaro.org
Date: Mon, 8 Apr 2013 16:45:40 +0530
Subject: workqueues: Introduce new flag WQ_POWER_EFFICIENT for power oriented
workqueues
Workqueues can be performance or power-oriented.
(Attached it too for applying cleanly)
---------x-------x-------
From: Viresh Kumar
Date: Mon, 8 Apr 2013 16:45:40 +0530
Subject: [PATCH V5 resent 1/5] workqueues: Introduce new flag
WQ_POWER_EFFICIENT for power oriented workqueues
Workqueues can be performance or power-
:40 +0530
Subject: [PATCH V5 resent 1/5] workqueues: Introduce new flag
WQ_POWER_EFFICIENT for power oriented workqueues
Workqueues can be performance or power-oriented. Currently, most workqueues are
bound to the CPU they were created on. This gives good performance (due to cache
effects
On 29 April 2013 21:49, Tejun Heo wrote:
> On Mon, Apr 29, 2013 at 12:06:28PM +0530, Viresh Kumar wrote:
> Yeap, !WQ_UNBOUND workqueues == per-cpu workqueues.
Sigh!! You were talking about thread per cpu here... Sorry for missing
it earlier :(
>> At this time local cpu may be busy or idle
Hello,
On Mon, Apr 29, 2013 at 12:06:28PM +0530, Viresh Kumar wrote:
> Whatever you wrote above confused me even more :)
Heh heh, confumageddon
> This is what i had in my mind until now. Its not about per-cpu workqueue.
>
> Lets take example of system_wq. It doesn't have WQ_UNBOUND flag
Hey Tejun,
On 27 April 2013 00:41, Tejun Heo wrote:
> 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.
Obviously. I understand this and agree with you on it. It
Hey Tejun,
On 27 April 2013 00:41, Tejun Heo t...@kernel.org wrote:
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.
Obviously. I understand this and agree with you on
Hello,
On Mon, Apr 29, 2013 at 12:06:28PM +0530, Viresh Kumar wrote:
Whatever you wrote above confused me even more :)
Heh heh, confumageddon
This is what i had in my mind until now. Its not about per-cpu workqueue.
Lets take example of system_wq. It doesn't have WQ_UNBOUND flag set.
On 29 April 2013 21:49, Tejun Heo t...@kernel.org wrote:
On Mon, Apr 29, 2013 at 12:06:28PM +0530, Viresh Kumar wrote:
Yeap, !WQ_UNBOUND workqueues == per-cpu workqueues.
Sigh!! You were talking about thread per cpu here... Sorry for missing
it earlier :(
At this time local cpu may be busy or
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
> +
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
+
-x-
>>
>> From: Viresh Kumar
>> Date: Mon, 8 Apr 2013 16:45:40 +0530
>> Subject: [PATCH V5 1/5] workqueues: Introduce new flag WQ_POWER_EFFICIENT for
>> power oriented workqueues
>>
>> Workqueues can be performance or power-oriented
40 +0530
> Subject: [PATCH V5 1/5] workqueues: Introduce new flag WQ_POWER_EFFICIENT for
> power oriented workqueues
>
> Workqueues can be performance or power-oriented. Currently, most workqueues
> are
> bound to the CPU they were created on. This gives good performance (due to
&g
:45:40 +0530
Subject: [PATCH V5 1/5] workqueues: Introduce new flag WQ_POWER_EFFICIENT for
power oriented workqueues
Workqueues can be performance or power-oriented. Currently, most workqueues
are
bound to the CPU they were created on. This gives good performance (due to
cache
effects
-
From: Viresh Kumar viresh.ku...@linaro.org
Date: Mon, 8 Apr 2013 16:45:40 +0530
Subject: [PATCH V5 1/5] workqueues: Introduce new flag WQ_POWER_EFFICIENT for
power oriented workqueues
Workqueues can be performance or power-oriented. Currently, most workqueues
are
bound to the CPU
te may break it. Please
consider applying this series if it looks fine to you.
---xx-
From: Viresh Kumar
Date: Mon, 8 Apr 2013 16:45:40 +0530
Subject: [PATCH V5 1/5] workqueues: Introduce new flag WQ_POWER_EFFICIENT for
power oriented workqueues
Work
On Wed, Apr 24, 2013 at 05:57:09PM +0530, Viresh Kumar wrote:
> If this line is not present i believe it is 'default n' only. So, i skipped
> it.
I think the difference is that when you configure the option for the
first time - ie. building kernel with .config used for an older kernel
- that it
On 24 April 2013 17:50, Amit Kucheria wrote:
> On Wed, Apr 24, 2013 at 5:12 PM, Viresh Kumar wrote:
>> +config WQ_POWER_EFFICIENT
>> + bool "Workqueue allocated as UNBOUND (by default) for power
>> efficiency"
>> + depends on PM
>
> default n
If this line is not present i believe
On Wed, Apr 24, 2013 at 5:12 PM, Viresh Kumar wrote:
> Workqueues can be performance or power oriented. For performance we may want
> to
> keep them running on a single cpu, so that it remains cache hot. For power we
> can give scheduler the liberty to choose target cpu for running work handler.
Workqueues can be performance or power oriented. For performance we may want to
keep them running on a single cpu, so that it remains cache hot. For power we
can give scheduler the liberty to choose target cpu for running work handler.
Later one (Power oriented WQ) can be achieved if the
Workqueues can be performance or power oriented. For performance we may want to
keep them running on a single cpu, so that it remains cache hot. For power we
can give scheduler the liberty to choose target cpu for running work handler.
Later one (Power oriented WQ) can be achieved if the
On Wed, Apr 24, 2013 at 5:12 PM, Viresh Kumar viresh.ku...@linaro.org wrote:
Workqueues can be performance or power oriented. For performance we may want
to
keep them running on a single cpu, so that it remains cache hot. For power we
can give scheduler the liberty to choose target cpu for
On 24 April 2013 17:50, Amit Kucheria amit.kuche...@linaro.org wrote:
On Wed, Apr 24, 2013 at 5:12 PM, Viresh Kumar viresh.ku...@linaro.org wrote:
+config WQ_POWER_EFFICIENT
+ bool Workqueue allocated as UNBOUND (by default) for power
efficiency
+ depends on PM
default n
If
On Wed, Apr 24, 2013 at 05:57:09PM +0530, Viresh Kumar wrote:
If this line is not present i believe it is 'default n' only. So, i skipped
it.
I think the difference is that when you configure the option for the
first time - ie. building kernel with .config used for an older kernel
- that it
as gmail's copy-paste may break it. Please
consider applying this series if it looks fine to you.
---xx-
From: Viresh Kumar viresh.ku...@linaro.org
Date: Mon, 8 Apr 2013 16:45:40 +0530
Subject: [PATCH V5 1/5] workqueues: Introduce new flag
26 matches
Mail list logo
