From: Viresh Kumar <viresh.kumar@linaro.org>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/6] cpufreq: governor: replace per-cpu delayed work with timers
Date: Mon, 30 Nov 2015 19:05:26 +0530 [thread overview]
Message-ID: <20151130133526.GD4899@ubuntu> (raw)
In-Reply-To: <1448885103.8275.31.camel@pengutronix.de>
On 30-11-15, 13:05, Lucas Stach wrote:
> I don't want to block this patch on that, but maybe as a thought for
> further consideration: Wouldn't it make sense to use a single unbound
> deferrable work item for this? There was some work to make this possible
> already: "timer: make deferrable cpu unbound timers really not bound to
> a cpu"
Yes, it would be sensible but that work has gone nowhere since April.
Once that is merged, we can think about it.
--
viresh
next prev parent reply other threads:[~2015-11-30 13:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1446121217.git.viresh.kumar@linaro.org>
2015-10-29 12:27 ` [PATCH 1/6] cpufreq: ondemand: Update sampling rate only for concerned policies Viresh Kumar
2015-12-03 2:16 ` Rafael J. Wysocki
2015-10-29 12:27 ` [PATCH 2/6] cpufreq: ondemand: Work is guaranteed to be pending Viresh Kumar
2015-10-29 12:27 ` [PATCH 3/6] cpufreq: governor: Pass policy as argument to ->gov_dbs_timer() Viresh Kumar
2015-10-29 12:27 ` [PATCH 4/6] cpufreq: governor: initialize/destroy timer_mutex with 'shared' Viresh Kumar
2015-10-29 12:27 ` [PATCH 5/6] cpufreq: governor: replace per-cpu delayed work with timers Viresh Kumar
2015-10-30 20:46 ` Ashwin Chaugule
2015-10-31 2:36 ` Viresh Kumar
2015-11-03 19:01 ` Ashwin Chaugule
2015-11-30 12:05 ` Lucas Stach
2015-11-30 13:35 ` Viresh Kumar [this message]
2015-10-29 12:27 ` [PATCH 6/6] cpufreq: ondemand: update update_sampling_rate() to make it more efficient Viresh Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151130133526.GD4899@ubuntu \
--to=viresh.kumar@linaro.org \
--cc=l.stach@pengutronix.de \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).