Linux NFS development
 help / color / mirror / Atom feed
From: Mike Owen <mjnowen@gmail.com>
To: Jeff Layton <jlayton@kernel.org>, Steve Dickson <steved@redhat.com>
Cc: 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>,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH nfs-utils v2] nfsdctl: add support for min-threads parameter
Date: Fri, 23 Jan 2026 19:21:53 +0000	[thread overview]
Message-ID: <2b7b02aa-8759-43c4-9cd1-04a57b13cf8f@gmail.com> (raw)
In-Reply-To: <20260123-minthreads-v2-1-9bfbae745845@kernel.org>

On 23/01/2026 18:48, Jeff Layton wrote:
> and the thread count will dynamically fluctuate between
> the min and max based on load.

Can "load" be described further in the manpage for users? I ask, because I'm interested to understand the heuristics it takes into account when nfsd makes a decision to increase or decrease the thread count. For example, is memory pressure + io pressure stall info + io requests all taken into account? A popular doc that is referenced in such discussions is here: [0].
[0]: https://utcc.utoronto.ca/~cks/space/blog/linux/NFSServerHowManyThreads


  reply	other threads:[~2026-01-23 19:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23 18:48 [PATCH nfs-utils v2] nfsdctl: add support for min-threads parameter Jeff Layton
2026-01-23 19:21 ` Mike Owen [this message]
2026-01-23 19:59   ` Jeff Layton
2026-02-01 17:31 ` Steve Dickson

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=2b7b02aa-8759-43c4-9cd1-04a57b13cf8f@gmail.com \
    --to=mjnowen@gmail.com \
    --cc=Dai.Ngo@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=okorniev@redhat.com \
    --cc=steved@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