From: Tejun Heo <tj@kernel.org>
To: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
Cc: Mark Fasheh <mfasheh@suse.com>, Joel Becker <jlbec@evilplan.org>,
Andrew Morton <akpm@linux-foundation.org>,
Joseph Qi <joseph.qi@huawei.com>,
xuejiufei <xuejiufei@huawei.com>,
"Norton.Zhu" <norton.zhu@huawei.com>,
Jun Piao <piaojun@huawei.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Michal Hocko <mhocko@suse.com>,
Vladimir Davydov <vdavydov@virtuozzo.com>,
Johannes Weiner <hannes@cmpxchg.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] fs/ocfs2/dlm: Remove deprecated create_singlethread_workqueue
Date: Wed, 31 Aug 2016 10:31:40 -0400 [thread overview]
Message-ID: <20160831143140.GU12660@htj.duckdns.org> (raw)
In-Reply-To: <2b5ad8d6688effe1a9ddb2bc2082d26fbbe00302.1472590094.git.bhaktipriya96@gmail.com>
On Wed, Aug 31, 2016 at 02:21:26AM +0530, Bhaktipriya Shridhar wrote:
> The workqueue "dlm_worker" queues a single work item &dlm->dispatched_work
> and thus 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 there are fixed number of work items, explicit concurrency
> limit is unnecessary here.
>
> Signed-off-by: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
Just for the record,
Acked-by: Tejun Heo <tj@kernel.org>
Thanks.
--
tejun
prev parent reply other threads:[~2016-08-31 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1472590094.git.bhaktipriya96@gmail.com>
2016-08-30 20:49 ` [PATCH v2 1/4] fs/ocfs2/dlmfs: " Bhaktipriya Shridhar
2016-08-30 20:50 ` [PATCH v2 2/4] fs/ocfs2/cluster: " Bhaktipriya Shridhar
2016-08-30 20:50 ` [PATCH v2 3/4] fs/ocfs2/super: " Bhaktipriya Shridhar
2016-08-30 20:51 ` [PATCH v2 4/4] fs/ocfs2/dlm: " Bhaktipriya Shridhar
2016-08-31 14:31 ` Tejun Heo [this message]
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=20160831143140.GU12660@htj.duckdns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bhaktipriya96@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hannes@cmpxchg.org \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@huawei.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=mhocko@suse.com \
--cc=norton.zhu@huawei.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=piaojun@huawei.com \
--cc=vdavydov@virtuozzo.com \
--cc=xuejiufei@huawei.com \
/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
all inboxes | Powered by JetHome®