linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: NFS regression between 5.17 and 5.18
Date: Thu, 28 Apr 2022 11:42:39 -0400	[thread overview]
Message-ID: <9d814666-6e95-e331-62a7-ec36fe1ca062@cornelisnetworks.com> (raw)
In-Reply-To: <8E8485F8-F56F-4A93-85AC-44BD8436DF6A@oracle.com>

On 4/28/22 10:57 AM, Chuck Lever III wrote:
>> On Apr 28, 2022, at 9:05 AM, Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com> wrote:
>>
>> Hi NFS folks,
>>
>> I've noticed a pretty nasty regression in our NFS capability between 5.17 and
>> 5.18-rc1. I've tried to bisect but not having any luck. The problem I'm seeing
>> is it takes 3 minutes to copy a file from NFS to the local disk. When it should
>> take less than half a second, which it did up through 5.17.
>>
>> It doesn't seem to be network related, but can't rule that out completely.
>>
>> I tried to bisect but the problem can be intermittent. Some runs I'll see a
>> problem in 3 out of 100 cycles, sometimes 0 out of 100. Sometimes I'll see it
>> 100 out of 100.
> 
> It's not clear from your problem report whether the problem appears
> when it's the server running v5.18-rc or the client.

That's because I don't know which it is. I'll do a quick test and find out. I
was testing the same kernel across both nodes.

-Denny


  reply	other threads:[~2022-04-28 15:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 13:05 NFS regression between 5.17 and 5.18 Dennis Dalessandro
2022-04-28 14:57 ` Chuck Lever III
2022-04-28 15:42   ` Dennis Dalessandro [this message]
2022-04-28 19:47     ` Dennis Dalessandro
2022-04-28 19:56       ` Trond Myklebust
2022-04-29 12:54         ` Dennis Dalessandro
2022-04-29 13:37           ` Chuck Lever III
2022-05-06 13:24             ` Dennis Dalessandro
2022-05-13 11:58               ` Dennis Dalessandro
2022-05-13 13:30                 ` Trond Myklebust
2022-05-13 14:59                   ` Chuck Lever III
2022-05-13 15:19                     ` Trond Myklebust
2022-05-13 18:53                       ` Chuck Lever III
2022-05-17 13:40                     ` Dennis Dalessandro
2022-05-17 14:02                       ` Chuck Lever III
2022-06-20  7:46                         ` Thorsten Leemhuis
2022-06-20 14:11                           ` Chuck Lever III
2022-06-20 14:29                             ` Thorsten Leemhuis
2022-06-20 14:40                               ` Chuck Lever III
2022-06-20 17:06                                 ` Dennis Dalessandro
2022-06-21 16:04                                   ` Olga Kornievskaia
2022-06-21 16:58                                     ` Dennis Dalessandro
2022-06-21 17:51                                       ` Olga Kornievskaia
2022-06-21 17:53                                         ` Chuck Lever III
2022-05-04  9:45 ` Thorsten Leemhuis

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=9d814666-6e95-e331-62a7-ec36fe1ca062@cornelisnetworks.com \
    --to=dennis.dalessandro@cornelisnetworks.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.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;
as well as URLs for NNTP newsgroup(s).