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 <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Subject: Re: [PATCH 0/2] nfsd: don't use sv_nrthreads in connection limiting
Date: Mon, 09 Dec 2024 09:54:06 -0500 [thread overview]
Message-ID: <ea34b105d4c4149000a6f10a7b0e68ac2033ac8e.camel@kernel.org> (raw)
In-Reply-To: <20241209004310.728309-1-neilb@suse.de>
On Mon, 2024-12-09 at 11:41 +1100, NeilBrown wrote:
> This is a resend of a couple of patches from a series that didn't get
> accepted in its entirety, but I think these patches were not objected
> to. Hopefully they can land so that when I get back to the series it
> will be smaller.
>
> Thanks,
> NeilBrown
>
>
The new heuristic makes a lot more sense than the hard cap that we have
now:
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2024-12-09 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 0:41 [PATCH 0/2] nfsd: don't use sv_nrthreads in connection limiting NeilBrown
2024-12-09 0:41 ` [PATCH 1/2] nfsd: don't use sv_nrthreads in connection limiting calculations NeilBrown
2024-12-09 17:25 ` Chuck Lever
2024-12-09 0:41 ` [PATCH 2/2] sunrpc: remove all connection limit configuration NeilBrown
2024-12-09 17:27 ` Chuck Lever
2024-12-10 12:29 ` Jeff Layton
2024-12-11 3:48 ` NeilBrown
2024-12-09 14:54 ` Jeff Layton [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=ea34b105d4c4149000a6f10a7b0e68ac2033ac8e.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--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