linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@poochiereds.net>
Cc: Tejun Heo <tj@kernel.org>,
	Bhaktipriya Shridhar <bhaktipriya96@gmail.com>,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] fs/nfsd/nfs4callback: Remove deprecated create_singlethread_workqueue
Date: Wed, 9 Nov 2016 15:23:59 -0500	[thread overview]
Message-ID: <20161109202359.GC4952@fieldses.org> (raw)
In-Reply-To: <20161109194724.GB4952@fieldses.org>

On Wed, Nov 09, 2016 at 02:47:24PM -0500, J. Bruce Fields wrote:
> For now I wish we could just like to continue assuming the workqueue
> processes only one item at a time.  Do we have that now, or do we need
> to switch to (looking at workqueue.h...) alloc_ordered workqueue()?

Oh, wait, I missed the _ordered_ in:

	#define create_singlethread_workqueue(name) \
	        alloc_ordered_workqueue("%s", __WQ_LEGACY | WQ_MEM_RECLAIM, name)

So our existing create_singlethread_workqueue is fine--but we probably
don't need those flags:

--b.

diff --git a/fs/nfsd/nfs4callback.c b/fs/nfsd/nfs4callback.c
index 211dc2aed8e1..eb78109d666c 100644
--- a/fs/nfsd/nfs4callback.c
+++ b/fs/nfsd/nfs4callback.c
@@ -1061,7 +1061,7 @@ static const struct rpc_call_ops nfsd4_cb_ops = {
 
 int nfsd4_create_callback_queue(void)
 {
-	callback_wq = create_singlethread_workqueue("nfsd4_callbacks");
+	callback_wq = alloc_ordered_workqueue("nfsd4_callbacks", 0);
 	if (!callback_wq)
 		return -ENOMEM;
 	return 0;

  reply	other threads:[~2016-11-09 20:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30 20:53 [PATCH v2] fs/nfsd/nfs4callback: Remove deprecated create_singlethread_workqueue Bhaktipriya Shridhar
2016-08-30 21:07 ` Jeff Layton
2016-08-31 14:39   ` Tejun Heo
2016-08-31 15:01     ` Jeff Layton
2016-11-08 21:39 ` J. Bruce Fields
2016-11-08 22:52   ` Tejun Heo
2016-11-09  1:27     ` J. Bruce Fields
2016-11-09 13:18       ` Jeff Layton
2016-11-09 15:08         ` Trond Myklebust
2016-11-09 15:17           ` Jeff Layton
2016-11-09 16:27         ` J. Bruce Fields
2016-11-09 17:33           ` Jeff Layton
2016-11-09 19:47             ` J. Bruce Fields
2016-11-09 20:23               ` J. Bruce Fields [this message]
2016-11-09 22:35                 ` Jeff Layton

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=20161109202359.GC4952@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bhaktipriya96@gmail.com \
    --cc=jlayton@poochiereds.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --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).