From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 34C663EFD28; Thu, 5 Feb 2026 14:19:58 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770301198; cv=none; b=MlehlZ1RerhpnWjbO0ZbaTiBotX8brpbgRwR/X3qn4RZRJ2iMJJUERxGZVV4cqvgyyXm2iMKVz9z4UcSDZBobEn6DCxNeat3LOp1e3dn4c2IaEqnknDtTtkQVbN0LW+hKBKKRPdXxb2zrjrbYwzds4uni8a+aSDEiHcMhb8hbfw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770301198; c=relaxed/simple; bh=wxz0xiJpsKFC77EfDP9XcC1ROIL9BC7+HETWtxtvbP8=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=uxbpDc8voS+8GXm5XbC/M6pUoIL3Lgjx6z0iUwlw/HGNRC0Uhyk/K3aBMx4MdxfCPXmijd9HXLU2QvX9z0vSkzlCOlvvRLDsUEHuS9GRP8Y6/+i/nsbpNaaHEKTaHLsI7hWBrZAPi/NQXSN/ktWIjM21vovUfSN7BW8kvj6+LV8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=WJ0QOupL; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="WJ0QOupL" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 40AD9C116D0; Thu, 5 Feb 2026 14:19:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1770301198; bh=wxz0xiJpsKFC77EfDP9XcC1ROIL9BC7+HETWtxtvbP8=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=WJ0QOupL1dj2b1OwhrsvJLPhJfAGcrPCz1b7N6aaJjBlfxWfS0gxaWGJk75+ib3LV xOTPBbLYL0jMnpn4+S9kubG1hfOBibReU32nSG9MdXMv0ASiHK13NpGFSN18M8bVMT 2jqv8EeDfBCgdv6OuGHDuLzsk/IJVmlgB6HCVuo9QvkBZ7LoaWUgdHIV6sEC/lmUuL MrnKFVQsN+aiLrnQN0krzljW8Gt1yL2mOl0zDKQ7GoTTf/GvF93zvFFyoBbfwBwrpL L7IjmBUuY/TWNhOaU3qvDlV3A0I+9CEbSwttcLSwjR4StcVKZ0fSujHzRYgvgou8wY vxya3dl4Yt4tA== Message-ID: <54cff24b-f010-4824-9b56-34beabf63401@kernel.org> Date: Thu, 5 Feb 2026 09:19:56 -0500 Precedence: bulk X-Mailing-List: linux-nfs@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] nfsd: report the requested maximum number of threads instead of number running To: Jeff Layton , Mike Owen , Chuck Lever , NeilBrown , Olga Kornievskaia , Dai Ngo , Tom Talpey Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org References: <20260204-minthreads-v1-1-7480176baf35@kernel.org> <2abf7a33-789f-405d-8993-8fbf30153aaa@app.fastmail.com> <6944906a-9256-4f10-88fa-822a639eb5eb@gmail.com> Content-Language: en-US From: Chuck Lever Organization: kernel.org In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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