From: Chuck Lever III <chuck.lever@oracle.com>
To: Timo Rothenpieler <timo@rothenpieler.org>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
linux-rdma <linux-rdma@vger.kernel.org>
Subject: Re: Spurious instability with NFSoRDMA under moderate load
Date: Mon, 21 Jun 2021 16:28:43 +0000 [thread overview]
Message-ID: <388908AD-FC71-4A4D-8314-B0C3F8EF127E@oracle.com> (raw)
In-Reply-To: <daae674a-84d4-de36-336d-693dc582e3ef@rothenpieler.org>
> On Jun 21, 2021, at 12:06 PM, Timo Rothenpieler <timo@rothenpieler.org> wrote:
>
> On 17.05.2021 19:37, Timo Rothenpieler wrote:
>> On 17.05.2021 18:27, Chuck Lever III wrote:
>>> Meanwhile, you could try 5.11 or 5.12 on your NFS server to see if
>>> the problem persists.
>> I updated the NFS server to 5.12.4 now and will observe and maybe try to cause some mixed load.
>
> Had this running on 5.12 for a month now, and haven't observed any kind of instability so far.
> So I'd carefully assume that something in after 5.10, that made it into 5.11 or 5.12 fixed or greatly improved the situation.
>
> Can't really sensibly bisect this sadly, given the extremely long and uncertain turnaround times.
Thank you for the update!
--
Chuck Lever
next prev parent reply other threads:[~2021-06-21 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 17:29 Spurious instability with NFSoRDMA under moderate load Timo Rothenpieler
2021-05-17 16:27 ` Chuck Lever III
2021-05-17 17:37 ` Timo Rothenpieler
2021-06-21 16:06 ` Timo Rothenpieler
2021-06-21 16:28 ` Chuck Lever III [this message]
2021-08-10 12:49 ` Timo Rothenpieler
[not found] ` <a28b403e-42cf-3189-a4db-86d20da1b7aa@rothenpieler.org>
2021-08-10 17:17 ` Chuck Lever III
2021-08-10 21:40 ` Timo Rothenpieler
[not found] ` <141fdf51-2aa1-6614-fe4e-96f168cbe6cf@rothenpieler.org>
2021-08-11 0:19 ` Chuck Lever III
2021-05-19 15:20 ` Leon Romanovsky
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=388908AD-FC71-4A4D-8314-B0C3F8EF127E@oracle.com \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=timo@rothenpieler.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