From: Petko Manolov <petkan@mip-labs.com>
To: Tejun Heo <tj@kernel.org>,
Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
Cc: Petko Manolov <petkan@nucleusys.com>,
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: Wed, 31 Aug 2016 17:27:51 +0300 [thread overview]
Message-ID: <E774CB24-BD0A-41AE-B414-FBC8BFD5447E@mip-labs.com> (raw)
In-Reply-To: <20160831142305.GI12660@htj.duckdns.org>
On August 31, 2016 5:23:05 PM GMT+03:00, Tejun Heo <tj@kernel.org> wrote:
>On Tue, Aug 30, 2016 at 10:02:47PM +0530, 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>
>
>Acked-by: Tejun Heo <tj@kernel.org>
>
>Thanks.
Acked-by: Petko Manolov <petkan@mip-labs.com>
cheers,
Petko
next prev parent reply other threads:[~2016-08-31 14:28 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
2016-08-31 14:23 ` Tejun Heo
2016-08-31 14:27 ` Petko Manolov [this message]
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=E774CB24-BD0A-41AE-B414-FBC8BFD5447E@mip-labs.com \
--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;
as well as URLs for NNTP newsgroup(s).