[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1391160084.4141.1.camel@jlt4.sipsolutions.net>
Date: Fri, 31 Jan 2014 10:21:24 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Zoran Markovic <zoran.markovic@...aro.org>, tj@...nel.org
Cc: linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
netdev@...r.kernel.org, Shaibal Dutta <shaibal.dutta@...adcom.com>,
"John W. Linville" <linville@...driver.com>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [RFC PATCH] net: wireless: move regulatory timeout work to
power efficient workqueue
On Thu, 2014-01-30 at 15:08 -0800, Zoran Markovic wrote:
> From: Shaibal Dutta <shaibal.dutta@...adcom.com>
>
> For better use of CPU idle time, allow the scheduler to select the CPU
> on which the timeout work of regulatory settings would be executed.
> This extends CPU idle residency time and saves power.
>
> This functionality is enabled when CONFIG_WQ_POWER_EFFICIENT is selected.
> - schedule_delayed_work(®_timeout, msecs_to_jiffies(3142));
> + queue_delayed_work(system_power_efficient_wq,
> + ®_timeout, msecs_to_jiffies(3142));
I'm not sure if this is part of a larger patchset actually adding that
"system_power_efficient_wq", but maybe it'd be better to expose a
function as an API rather than the wq struct?
Something like
scheduled_delayed_work_pwr_efficient(...)?
?
johannes
--
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/
Powered by blists - more mailing lists