From: Petko Manolov <petkan@mip-labs.com>
To: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
Cc: Petko Manolov <petkan@nucleusys.com>, Tejun Heo <tj@kernel.org>,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: pegasus: Remove deprecated create_singlethread_workqueue
Date: Tue, 30 Aug 2016 19:41:48 +0300 [thread overview]
Message-ID: <20160830164148.fz4tbei5g7dlma4n@p310> (raw)
In-Reply-To: <20160830163247.GA25925@Karyakshetra>
On 16-08-30 22:02:47, Bhaktipriya Shridhar wrote:
> The workqueue "pegasus_workqueue" queues a single work item per pegasus
> instance and hence it doesn't require execution ordering. Hence,
> alloc_workqueue has been used to replace the deprecated
> create_singlethread_workqueue instance.
>
> The WQ_MEM_RECLAIM flag has been set to ensure forward progress under
> memory pressure since it's a network driver.
>
> Since there are fixed number of work items, explicit concurrency
> limit is unnecessary here.
>
> Signed-off-by: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
> ---
> drivers/net/usb/pegasus.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/usb/pegasus.c b/drivers/net/usb/pegasus.c
> index 9bbe0161..1434e5d 100644
> --- a/drivers/net/usb/pegasus.c
> +++ b/drivers/net/usb/pegasus.c
> @@ -1129,7 +1129,8 @@ static int pegasus_probe(struct usb_interface *intf,
> return -ENODEV;
>
> if (pegasus_count == 0) {
> - pegasus_workqueue = create_singlethread_workqueue("pegasus");
> + pegasus_workqueue = alloc_workqueue("pegasus", WQ_MEM_RECLAIM,
> + 0);
> if (!pegasus_workqueue)
> return -ENOMEM;
> }
> --
> 2.1.4
Nope, there is no need for singlethread-ness here. As long as the flag you used
is doing the right thing i am OK with the patch.
Petko
next prev parent reply other threads:[~2016-08-30 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 16:32 [PATCH] net: pegasus: Remove deprecated create_singlethread_workqueue Bhaktipriya Shridhar
2016-08-30 16:41 ` Petko Manolov [this message]
2016-08-31 14:23 ` Tejun Heo
2016-08-31 14:27 ` Petko Manolov
2016-09-01 23:42 ` David Miller
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=20160830164148.fz4tbei5g7dlma4n@p310 \
--to=petkan@mip-labs.com \
--cc=bhaktipriya96@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petkan@nucleusys.com \
--cc=tj@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox