From: Jeff Layton <jlayton@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] fs/nfsd/nfs4callback: Remove deprecated create_singlethread_workqueue
Date: Wed, 31 Aug 2016 11:01:25 -0400 [thread overview]
Message-ID: <1472655685.5795.10.camel@redhat.com> (raw)
In-Reply-To: <20160831143953.GV12660@htj.duckdns.org>
On Wed, 2016-08-31 at 10:39 -0400, Tejun Heo wrote:
> Hello, Jeff.
>
> On Tue, Aug 30, 2016 at 05:07:23PM -0400, Jeff Layton wrote:
> >
> > Hah! I have almost exactly the same patch in my tree. I've only not
> > sent it because I haven't had the chance to test it well.
> >
> > The only difference in mine is that it passes in WQ_UNBOUND. ISTM
> > that
> > we don't really need a bound workqueue here since we only use this
> > to
> > kick off callbacks to the client. I doubt we'd get much out of
> > strictly
> > maintaining cache locality here, and we're better off just sending
> > it
> > the callback as quickly as possible.
>
> We recently broke strong locality guarantee for users which don't use
> queue_work_on(), so the default locality is now only for optimization
> instead of correctness anyway. Unless there are actual benefits to
> using WQ_UNBOUND, I think in general it's better to stick with as
> little attributes as possible so that we have more maneuvering room
> down the line. But, yeah, if this can impact performance in subtle
> ways, it could be best to just do an identity conversion at least for
> now.
>
> Thanks.
>
Ahh ok, thanks...that's good to know. If you think we don't need
WQ_UNBOUND then this is fine with me.
Reviewed-by: Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2016-08-31 15:01 UTC|newest]
Thread overview: 16+ 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 [this message]
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: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
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=1472655685.5795.10.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=bfields@fieldses.org \
--cc=bhaktipriya96@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.