From: Greg KH <gregkh@linuxfoundation.org>
To: Wolfgang Walter <linux@stwm.de>
Cc: stable@vger.kernel.org, Trond Myklebust <trondmy@gmail.com>,
Chuck Lever <chuck.lever@oracle.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 5.4.188 and later: massive performance regression with nfsd
Date: Wed, 11 May 2022 14:38:05 +0200 [thread overview]
Message-ID: <YnuuLZe6h80KCNhd@kroah.com> (raw)
In-Reply-To: <f8d9b9112607df4807fba8948ac6e145@stwm.de>
On Wed, May 11, 2022 at 12:03:13PM +0200, Wolfgang Walter wrote:
> Hi,
>
> starting with 5.4.188 wie see a massive performance regression on our
> nfs-server. It basically is serving requests very very slowly with cpu
> utilization of 100% (with 5.4.187 and earlier it is 10%) so that it is
> unusable as a fileserver.
>
> The culprit are commits (or one of it):
>
> c32f1041382a88b17da5736886da4a492353a1bb "nfsd: cleanup
> nfsd_file_lru_dispose()"
> 628adfa21815f74c04724abc85847f24b5dd1645 "nfsd: Containerise filecache
> laundrette"
>
> (upstream 36ebbdb96b694dd9c6b25ad98f2bbd263d022b63 and
> 9542e6a643fc69d528dfb3303f145719c61d3050)
>
> If I revert them in v5.4.192 the kernel works as before and performance is
> ok again.
>
> I did not try to revert them one by one as any disruption of our nfs-server
> is a severe problem for us and I'm not sure if they are related.
>
> 5.10 and 5.15 both always performed very badly on our nfs-server in a
> similar way so we were stuck with 5.4.
>
> I now think this is because of 36ebbdb96b694dd9c6b25ad98f2bbd263d022b63
> and/or 9542e6a643fc69d528dfb3303f145719c61d3050 though I didn't tried to
> revert them in 5.15 yet.
Odds are 5.18-rc6 is also a problem?
If so, I'll just wait for the fix to get into Linus's tree as this does
not seem to be a stable-tree-only issue.
thanks,
greg k-h
next prev parent reply other threads:[~2022-05-11 12:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 10:03 5.4.188 and later: massive performance regression with nfsd Wolfgang Walter
2022-05-11 12:38 ` Greg KH [this message]
2022-05-11 14:16 ` Chuck Lever III
2022-05-11 14:23 ` Greg KH
2022-05-11 14:36 ` Chuck Lever III
2022-05-11 15:30 ` Wolfgang Walter
2022-05-11 15:50 ` Chuck Lever III
2022-05-11 17:24 ` Wolfgang Walter
2022-05-20 15:36 ` Chuck Lever III
2022-05-20 16:40 ` Trond Myklebust
2022-05-20 17:06 ` dai.ngo
2022-05-20 21:52 ` Chuck Lever III
2022-05-20 22:24 ` Trond Myklebust
2022-05-20 23:43 ` Chuck Lever III
2022-05-21 17:22 ` Chuck Lever III
2022-05-21 18:10 ` Trond Myklebust
2022-05-21 19:11 ` Chuck Lever III
2022-05-21 19:49 ` Trond Myklebust
2022-05-21 20:41 ` Chuck Lever III
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=YnuuLZe6h80KCNhd@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux@stwm.de \
--cc=stable@vger.kernel.org \
--cc=trondmy@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox