From: Chuck Lever <cel@kernel.org>
To: Jeff Layton <jlayton@kernel.org>, Mike Owen <mjnowen@gmail.com>,
Chuck Lever <chuck.lever@oracle.com>, NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nfsd: report the requested maximum number of threads instead of number running
Date: Thu, 5 Feb 2026 09:19:56 -0500 [thread overview]
Message-ID: <54cff24b-f010-4824-9b56-34beabf63401@kernel.org> (raw)
In-Reply-To: <d0484cf69968e0415e4c0b9fca9217ebeca928e7.camel@kernel.org>
On 2/5/26 6:18 AM, Jeff Layton wrote:
> You won't be able to get to the min-threads setting from /proc. That's
> only available via netlink. If you enable dynamic threading (via
> netlink), then the traditional "th" count in /proc currently shows you
> the number of running threads. If this patch is applied, it'll show you
> the requested maximum instead.
>
> So, with this patch applied you can query both the min and max number
> of threads via netlink. We don't yet have an interface to query the
> number of threads currently running. In principle, you can get that
> info from "ps", but we could add that to the netlink interface if
> someone can make a good use-case for it.
I use `pgrep -c nfsd`
--
Chuck Lever
prev parent reply other threads:[~2026-02-05 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 17:23 [PATCH] nfsd: report the requested maximum number of threads instead of number running Jeff Layton
2026-02-04 18:51 ` Chuck Lever
2026-02-04 19:13 ` Jeff Layton
2026-02-05 10:01 ` Mike Owen
2026-02-05 11:18 ` Jeff Layton
2026-02-05 14:19 ` Chuck Lever [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=54cff24b-f010-4824-9b56-34beabf63401@kernel.org \
--to=cel@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mjnowen@gmail.com \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--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