From: Johannes Berg <johannes@sipsolutions.net>
To: Tejun Heo <tj@kernel.org>
Cc: Zoran Markovic <zoran.markovic@linaro.org>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org,
Shaibal Dutta <shaibal.dutta@broadcom.com>,
"John W. Linville" <linville@tuxdriver.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [RFC PATCH] net: wireless: move regulatory timeout work to power efficient workqueue
Date: Fri, 31 Jan 2014 10:42:23 +0100 [thread overview]
Message-ID: <1391161343.4141.3.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20140131093531.GA25559@mtj.dyndns.org> (sfid-20140131_103536_949453_61FB57CB)
On Fri, 2014-01-31 at 04:35 -0500, Tejun Heo wrote:
> Hello,
>
> On Fri, Jan 31, 2014 at 10:21:24AM +0100, Johannes Berg wrote:
> > 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(...)?
>
> While there are some benefits to using dedicated functions for
> specific workqueues, I don't think it brings enough benefits to
> justify adding dedicated API and am unlikely to add new ones.
Fair enough, I guess I'll take those patches in.
johannes
next prev parent reply other threads:[~2014-01-31 9:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 23:08 [RFC PATCH] net: wireless: move regulatory timeout work to power efficient workqueue Zoran Markovic
2014-01-30 23:08 ` Zoran Markovic
2014-01-31 9:21 ` Johannes Berg
2014-01-31 9:35 ` Tejun Heo
2014-01-31 9:35 ` Tejun Heo
2014-01-31 9:42 ` Johannes Berg [this message]
2014-02-05 9:17 ` Stanislaw Gruszka
2014-02-05 9:25 ` Tejun Heo
2014-02-05 9:25 ` Tejun Heo
2014-01-31 13:38 ` Johannes Berg
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=1391161343.4141.3.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=shaibal.dutta@broadcom.com \
--cc=tj@kernel.org \
--cc=zoran.markovic@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.