From: cel@kernel.org
To: Trond Myklebust <trondmy@kernel.org>,
Anna Schumaker <anna@kernel.org>, Neil Brown <neilb@suse.de>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
Jeff Layton <jlayton@kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sunrpc: add info about xprt queue times to svc_xprt_dequeue tracepoint
Date: Fri, 11 Apr 2025 10:53:15 -0400 [thread overview]
Message-ID: <174438318485.31035.4351288521914711713.b4-ty@oracle.com> (raw)
In-Reply-To: <20250411-sunrpc-tracepoints-v1-1-ed2eb14ce6ee@kernel.org>
From: Chuck Lever <chuck.lever@oracle.com>
On Fri, 11 Apr 2025 10:22:14 -0400, Jeff Layton wrote:
> I've been looking at a problem where we see increased RPC timeouts in
> clients when the nfs_layout_flexfiles dataserver_timeo value is tuned
> very low (6s). This is necessary to ensure quick failover to a different
> mirror if a server goes down, but it causes a lot more major RPC timeouts.
>
> Ultimately, the problem is server-side however. It's sometimes doesn't
> respond to connection attempts. My theory is that the interrupt handler
> runs when a connection comes in, the xprt ends up being enqueued, but it
> takes a significant amount of time for the nfsd thread to pick it up.
>
> [...]
Applied to nfsd-testing, thanks!
[1/1] sunrpc: add info about xprt queue times to svc_xprt_dequeue tracepoint
commit: b7a6405d13bb2b5cbf89decb111f84408d121dc9
--
Chuck Lever
prev parent reply other threads:[~2025-04-11 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 14:22 Jeff Layton
2025-04-11 14:53 ` cel [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=174438318485.31035.4351288521914711713.b4-ty@oracle.com \
--to=cel@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
--cc=trondmy@kernel.org \
/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
all inboxes | Powered by JetHome®