From: Mike Snitzer <snitzer@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: NeilBrown <neil@brown.name>, Jeff Layton <jlayton@kernel.org>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
linux-nfs@vger.kernel.org, linux-rdma@vger.kernel.org,
Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH v1] svcrdma: Increase the server's default RPC/RDMA credit grant
Date: Wed, 1 Oct 2025 18:44:58 -0400 [thread overview]
Message-ID: <aN2u6tt39GCNXRHO@kernel.org> (raw)
In-Reply-To: <2cfc0bf3-e1ee-46ab-9fa5-de6d0e39a3db@kernel.org>
On Wed, Oct 01, 2025 at 04:18:10PM -0400, Chuck Lever wrote:
> On 10/1/25 3:35 PM, Mike Snitzer wrote:
> > On Fri, Sep 26, 2025 at 11:52:35AM -0400, Chuck Lever wrote:
> >> From: Chuck Lever <chuck.lever@oracle.com>
> >>
> >> Now that the nfsd thread count can scale to more threads, permit
> >
> > Just trying to appreciate which change(s) paved the way for this
> > RPCRDMA_MAX_REQUESTS change.
> >
> > Are you referring to the netlink interface changes Jeff did earlier
> > this year or something else? (thinking "something else" but...)
> >
> > Might be useful to update the header to convey which specific
> > commit(s) made this change possible.
>
> The svc thread scaling change refers to the commits from
>
> e3274026e2ec ("SUNRPC: move all of xprt handling into svc_xprt_handle()")
>
> to
>
> 15d39883ee7d ("SUNRPC: change the back-channel queue to lwq")
>
> all dated about two years ago, merged in v6.7. Just checking,
> should the updated description provide more detail than that?
No, that's perfect. Thanks
prev parent reply other threads:[~2025-10-01 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 15:52 [PATCH v1] svcrdma: Increase the server's default RPC/RDMA credit grant Chuck Lever
2025-10-01 19:35 ` Mike Snitzer
2025-10-01 20:18 ` Chuck Lever
2025-10-01 22:44 ` Mike Snitzer [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=aN2u6tt39GCNXRHO@kernel.org \
--to=snitzer@kernel.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.