From: Jeff Layton <jlayton@kernel.org>
To: NeilBrown <neilb@suse.de>, Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org, Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Subject: Re: [PATCH 0/6] prepare for dynamic server thread management
Date: Tue, 28 Oct 2025 11:47:26 -0400 [thread overview]
Message-ID: <e03fd3e300b01be35f5c10e33f819f3991776706.camel@kernel.org> (raw)
In-Reply-To: <20241023024222.691745-1-neilb@suse.de>
On Wed, 2024-10-23 at 13:37 +1100, NeilBrown wrote:
> These patches prepare the way for demand-based adjustment of the number
> of server threads. They primarily remove some places there the
> configured thread count is used to configure other things.
>
> With these in place only two more patches are needed to have demand
> based thread count. The details of how to configure this need to be
> discussed to ensure we have considered all perspectives, and I would
> rather than happen in the context of two patches, not in the context of
> 8. So I'm sending these first in the hope that will land with minimal
> fuss. Once they do land I'll send the remainder (which you have already
> seen) and will look forward to a fruitful discussion.
>
> Thanks,
> NeilBrown
>
> [PATCH 1/6] SUNRPC: move nrthreads counting to start/stop threads.
> [PATCH 2/6] nfsd: return hard failure for OP_SETCLIENTID when there
> [PATCH 3/6] nfs: dynamically adjust per-client DRC slot limits.
> [PATCH 4/6] nfsd: don't use sv_nrthreads in connection limiting
> [PATCH 5/6] sunrpc: remove all connection limit configuration
> [PATCH 6/6] sunrpc: introduce possibility that requested number of
Hi Neil,
You sent this just over a year ago. It looks like this set didn't get
merged for some reason. Were you still pursuing this work? I have some
interest in seeing a dynamic thread count work, so if not I'd be
interested in picking up this work.
Thanks,
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-10-28 15:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 2:37 [PATCH 0/6] prepare for dynamic server thread management NeilBrown
2024-10-23 2:37 ` [PATCH 1/6] SUNRPC: move nrthreads counting to start/stop threads NeilBrown
2024-10-23 2:37 ` [PATCH 2/6] nfsd: return hard failure for OP_SETCLIENTID when there are too many clients NeilBrown
2024-10-23 13:42 ` Chuck Lever
2024-10-23 21:47 ` NeilBrown
2024-10-23 2:37 ` [PATCH 3/6] nfs: dynamically adjust per-client DRC slot limits NeilBrown
2024-10-23 11:48 ` Jeff Layton
2024-10-23 13:55 ` Chuck Lever
2024-10-23 16:34 ` Tom Talpey
2024-10-23 21:53 ` NeilBrown
2024-10-23 2:37 ` [PATCH 4/6] nfsd: don't use sv_nrthreads in connection limiting calculations NeilBrown
2024-10-23 12:08 ` Jeff Layton
2024-10-23 21:18 ` NeilBrown
2024-10-23 2:37 ` [PATCH 5/6] sunrpc: remove all connection limit configuration NeilBrown
2024-10-23 12:50 ` Jeff Layton
2024-10-23 2:37 ` [PATCH 6/6] sunrpc: introduce possibility that requested number of threads is different from actual NeilBrown
2024-10-23 13:32 ` Jeff Layton
2024-10-30 6:35 ` kernel test robot
2024-10-23 14:00 ` [PATCH 0/6] prepare for dynamic server thread management Chuck Lever
2025-10-28 15:47 ` Jeff Layton [this message]
2025-10-28 22:36 ` NeilBrown
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=e03fd3e300b01be35f5c10e33f819f3991776706.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=kolga@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tom@talpey.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