From: Chuck Lever via Bugspray Bot <bugbot@kernel.org>
To: iommu@lists.linux.dev, robin.murphy@arm.com, anna@kernel.org,
chuck.lever@oracle.com, jlayton@kernel.org, trondmy@kernel.org,
linux-nfs@vger.kernel.org, cel@kernel.org
Subject: Re: NFS Server Issues with RDMA in Kernel 6.13.6
Date: Mon, 24 Mar 2025 18:35:11 +0000 [thread overview]
Message-ID: <20250324-b219865c6-abed7f2a8789@bugzilla.kernel.org> (raw)
In-Reply-To: <20250313-b219865c0-2a34cbc6e249@bugzilla.kernel.org>
Chuck Lever writes via Kernel.org Bugzilla:
No progress. It looks like a long term structural problem that we won't be able to address quickly.
It would be good to confirm that the issue is indeed contention in the IOVA allocator. Compiling with LOCK_STAT enabled and looking in /proc/lock_stat would give some indication that Robin's theory in on the right track.
Meanwhile I plan to ask the RDMA gurus if there is an improvement that can be made in the svcrdma implementation to help address the problem. If you need immediately relief, reducing the NFSD thread count might help.
View: https://bugzilla.kernel.org/show_bug.cgi?id=219865#c6
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
next prev parent reply other threads:[~2025-03-24 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 18:35 NFS Server Issues with RDMA in Kernel 6.13.6 Lucas via Bugspray Bot
2025-03-13 18:44 ` Chuck Lever
2025-03-13 19:20 ` Lucas via Bugspray Bot
2025-03-14 10:43 ` Robin Murphy
2025-03-14 20:26 ` Chuck Lever
2025-03-24 16:55 ` Lucas via Bugspray Bot
2025-03-24 18:35 ` Chuck Lever via Bugspray Bot [this message]
2025-03-26 23:00 ` Lucas via Bugspray Bot
2025-04-01 14:10 ` Chuck Lever via Bugspray Bot
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=20250324-b219865c6-abed7f2a8789@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=anna@kernel.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=iommu@lists.linux.dev \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=robin.murphy@arm.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