* [PATCH] libertas_tf: Remove create_workqueue
@ 2016-06-07 20:08 Bhaktipriya Shridhar
2016-06-11 22:47 ` Tejun Heo
2016-06-29 15:42 ` Kalle Valo
0 siblings, 2 replies; 5+ messages in thread
From: Bhaktipriya Shridhar @ 2016-06-07 20:08 UTC (permalink / raw)
To: Kalle Valo, Johannes Berg; +Cc: Tejun Heo, linux-wireless, netdev, linux-kernel
alloc_workqueue replaces deprecated create_workqueue().
A dedicated workqueue has been used since the workitem (viz
&priv->cmd_work per priv, which maps to lbtf_cmd_work) is involved in
actual command processing and may be used on a memory reclaim path.
The workitems require forward progress under memory pressure and hence,
WQ_MEM_RECLAIM has been set. Since there are only a fixed number of work
items, explicit concurrency limit is unnecessary here.
Signed-off-by: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
---
drivers/net/wireless/marvell/libertas_tf/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/marvell/libertas_tf/main.c b/drivers/net/wireless/marvell/libertas_tf/main.c
index 0bf8916..81463f7 100644
--- a/drivers/net/wireless/marvell/libertas_tf/main.c
+++ b/drivers/net/wireless/marvell/libertas_tf/main.c
@@ -742,7 +742,7 @@ EXPORT_SYMBOL_GPL(lbtf_bcn_sent);
static int __init lbtf_init_module(void)
{
lbtf_deb_enter(LBTF_DEB_MAIN);
- lbtf_wq = create_workqueue("libertastf");
+ lbtf_wq = alloc_workqueue("libertastf", WQ_MEM_RECLAIM, 0);
if (lbtf_wq == NULL) {
printk(KERN_ERR "libertastf: couldn't create workqueue\n");
return -ENOMEM;
--
2.1.4
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH] libertas_tf: Remove create_workqueue
2016-06-07 20:08 [PATCH] libertas_tf: Remove create_workqueue Bhaktipriya Shridhar
@ 2016-06-11 22:47 ` Tejun Heo
2016-06-28 16:50 ` Bhaktipriya Shridhar
2016-06-29 15:42 ` Kalle Valo
1 sibling, 1 reply; 5+ messages in thread
From: Tejun Heo @ 2016-06-11 22:47 UTC (permalink / raw)
To: Bhaktipriya Shridhar
Cc: Kalle Valo, Johannes Berg, linux-wireless, netdev, linux-kernel
On Wed, Jun 08, 2016 at 01:38:53AM +0530, Bhaktipriya Shridhar wrote:
> alloc_workqueue replaces deprecated create_workqueue().
>
> A dedicated workqueue has been used since the workitem (viz
> &priv->cmd_work per priv, which maps to lbtf_cmd_work) is involved in
> actual command processing and may be used on a memory reclaim path.
> The workitems require forward progress under memory pressure and hence,
> WQ_MEM_RECLAIM has been set. Since there are only a fixed number of work
> items, explicit concurrency limit is unnecessary here.
>
> Signed-off-by: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
Acked-by: Tejun Heo <tj@kernel.org>
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] libertas_tf: Remove create_workqueue
2016-06-11 22:47 ` Tejun Heo
@ 2016-06-28 16:50 ` Bhaktipriya Shridhar
2016-06-28 17:02 ` Kalle Valo
0 siblings, 1 reply; 5+ messages in thread
From: Bhaktipriya Shridhar @ 2016-06-28 16:50 UTC (permalink / raw)
To: Tejun Heo
Cc: Kalle Valo, Johannes Berg, linux-wireless, netdev,
Linux-Kernel@Vger. Kernel. Org
Ping!
Thanks,
Bhaktipriya
On Sun, Jun 12, 2016 at 4:17 AM, Tejun Heo <tj@kernel.org> wrote:
> On Wed, Jun 08, 2016 at 01:38:53AM +0530, Bhaktipriya Shridhar wrote:
>> alloc_workqueue replaces deprecated create_workqueue().
>>
>> A dedicated workqueue has been used since the workitem (viz
>> &priv->cmd_work per priv, which maps to lbtf_cmd_work) is involved in
>> actual command processing and may be used on a memory reclaim path.
>> The workitems require forward progress under memory pressure and hence,
>> WQ_MEM_RECLAIM has been set. Since there are only a fixed number of work
>> items, explicit concurrency limit is unnecessary here.
>>
>> Signed-off-by: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
>
> Acked-by: Tejun Heo <tj@kernel.org>
>
> Thanks.
>
> --
> tejun
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] libertas_tf: Remove create_workqueue
2016-06-28 16:50 ` Bhaktipriya Shridhar
@ 2016-06-28 17:02 ` Kalle Valo
0 siblings, 0 replies; 5+ messages in thread
From: Kalle Valo @ 2016-06-28 17:02 UTC (permalink / raw)
To: Bhaktipriya Shridhar
Cc: Tejun Heo, Johannes Berg, linux-wireless, netdev,
Linux-Kernel@Vger. Kernel. Org
Bhaktipriya Shridhar <bhaktipriya96@gmail.com> writes:
> Ping!
I'm lagging behind, the patch is still on my queue:
https://patchwork.kernel.org/patch/9162447/
Please don't top most, it's annoying.
--
Kalle Valo
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: libertas_tf: Remove create_workqueue
2016-06-07 20:08 [PATCH] libertas_tf: Remove create_workqueue Bhaktipriya Shridhar
2016-06-11 22:47 ` Tejun Heo
@ 2016-06-29 15:42 ` Kalle Valo
1 sibling, 0 replies; 5+ messages in thread
From: Kalle Valo @ 2016-06-29 15:42 UTC (permalink / raw)
To: Bhaktipriya Shridhar
Cc: Johannes Berg, Tejun Heo, linux-wireless, netdev, linux-kernel
Bhaktipriya Shridhar <bhaktipriya96@gmail.com> wrote:
> alloc_workqueue replaces deprecated create_workqueue().
>
> A dedicated workqueue has been used since the workitem (viz
> &priv->cmd_work per priv, which maps to lbtf_cmd_work) is involved in
> actual command processing and may be used on a memory reclaim path.
> The workitems require forward progress under memory pressure and hence,
> WQ_MEM_RECLAIM has been set. Since there are only a fixed number of work
> items, explicit concurrency limit is unnecessary here.
>
> Signed-off-by: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
> Acked-by: Tejun Heo <tj@kernel.org>
Thanks, 1 patch applied to wireless-drivers-next.git:
452fa86e9806 libertas_tf: Remove create_workqueue
--
Sent by pwcli
https://patchwork.kernel.org/patch/9162447/
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2016-06-29 15:43 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-06-07 20:08 [PATCH] libertas_tf: Remove create_workqueue Bhaktipriya Shridhar
2016-06-11 22:47 ` Tejun Heo
2016-06-28 16:50 ` Bhaktipriya Shridhar
2016-06-28 17:02 ` Kalle Valo
2016-06-29 15:42 ` Kalle Valo
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).