[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <54cff24b-f010-4824-9b56-34beabf63401@kernel.org>
Date: Thu, 5 Feb 2026 09:19:56 -0500
From: Chuck Lever <cel@...nel.org>
To: Jeff Layton <jlayton@...nel.org>, Mike Owen <mjnowen@...il.com>,
Chuck Lever <chuck.lever@...cle.com>, NeilBrown <neil@...wn.name>,
Olga Kornievskaia <okorniev@...hat.com>, Dai Ngo <Dai.Ngo@...cle.com>,
Tom Talpey <tom@...pey.com>
Cc: linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nfsd: report the requested maximum number of threads
instead of number running
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
Powered by blists - more mailing lists