From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfsd: queue laundrette to filecache_wq instead of system_wq
Date: Mon, 07 Nov 2022 10:55:04 -0500 [thread overview]
Message-ID: <561afeb91cee368db445ac74561bc6189a24fdef.camel@kernel.org> (raw)
In-Reply-To: <2FC9BEB2-189B-4EF6-AC61-40263BC47737@oracle.com>
On Mon, 2022-11-07 at 15:11 +0000, Chuck Lever III wrote:
> Hi Jeff -
>
> > On Nov 7, 2022, at 10:01 AM, Jeff Layton <jlayton@kernel.org> wrote:
> >
> > nfsd has grown a dedicated workqueue for the filecache, but this job is
> > still queued to the system_wq. Change it to use the filecache_wq.
>
> Actually... there doesn't seem to be anything special about
> nfsd_filecache_wq. 9542e6a643fc ("nfsd: Containerise filecache
> laundrette") does not make clear why it was added.
>
> Playing devil's advocate: why not make the converse change and
> replace it with system_wq?
>
Good question.
At one time, allocating a workqueue gave you a dedicated pool of
threads, but that's no longer the case.
Documentation/core-api/workqueue.rst says: "A wq no longer manages
execution resources but serves as a domain for forward progress
guarantee, flush and work item attributes."
Given that we're allocating this workqueue exactly the same way we
allocate the system_wq, I don't think we need our own workqueue at all.
I'd be fine with changing this to be the reverse if you prefer.
>
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > ---
> > fs/nfsd/filecache.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/fs/nfsd/filecache.c b/fs/nfsd/filecache.c
> > index 1e76b0d3b83a..018fd1565193 100644
> > --- a/fs/nfsd/filecache.c
> > +++ b/fs/nfsd/filecache.c
> > @@ -212,7 +212,7 @@ static void
> > nfsd_file_schedule_laundrette(void)
> > {
> > if (test_bit(NFSD_FILE_CACHE_UP, &nfsd_file_flags))
> > - queue_delayed_work(system_wq, &nfsd_filecache_laundrette,
> > + queue_delayed_work(nfsd_filecache_wq, &nfsd_filecache_laundrette,
> > NFSD_LAUNDRETTE_DELAY);
> > }
> >
> > --
> > 2.38.1
> >
>
> --
> Chuck Lever
>
>
>
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2022-11-07 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 15:01 [PATCH] nfsd: queue laundrette to filecache_wq instead of system_wq Jeff Layton
2022-11-07 15:11 ` Chuck Lever III
2022-11-07 15:55 ` Jeff Layton [this message]
2022-11-07 15:56 ` Chuck Lever III
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=561afeb91cee368db445ac74561bc6189a24fdef.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.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