From: Chuck Lever <chuck.lever@oracle.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: long-term stable backports of NFSD patches
Date: Wed, 8 May 2024 09:43:40 -0400 [thread overview]
Message-ID: <ZjuBjMsY/ZpRjPk1@tissot.1015granger.net> (raw)
In-Reply-To: <CAOQ4uxjNK95-PgHoZ+HzBGE4F7BhZiC4sSPcJAR8e+gYmyN_dg@mail.gmail.com>
On Wed, May 08, 2024 at 02:29:05PM +0300, Amir Goldstein wrote:
> On Mon, May 6, 2024 at 4:25 PM Chuck Lever <chuck.lever@oracle.com> wrote:
> >
> > It's apparent that a number of distributions and their customers
> > remain on long-term stable kernels. We are aware of the scalability
> > problems and other bugs in NFSD in kernels between v5.4 and v6.1.
> >
>
> Chuck,
>
> Are you able to share a partial list of scalability problems that were
> fixed by this backport series?
>
> Specifically, my interest is in the list of improvements to 5.15.y.
In broad strokes:
- The garbage collection mechanism was rewritten to keep the LRU
list short, and to keep sweeps productive. This was the main issue
as the LRU used to have hundreds of thousands of files on it and
one sweep would take so much CPU it was reported as a soft lockup.
- NFSv4 OPEN files are no longer garbage collected so that an NFSv4
CLOSE means local accessors have immediate access to a file.
- The filecache hash table is converted to an rhltable so that it
can efficiently manage many more open files.
- Various fixes prevent writeback of garbage-collected files from
bogging down.
There are a handful of important bugfixes before this commit, but
starting with commit 0369b53886ec ("NFSD: Report filecache LRU
size"), have a look at the commits that touch fs/nfsd/filecache.c.
--
Chuck Lever
next prev parent reply other threads:[~2024-05-08 13:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 13:24 long-term stable backports of NFSD patches Chuck Lever
2024-05-08 11:29 ` Amir Goldstein
2024-05-08 13:43 ` Chuck Lever [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-20 14:57 Chuck Lever
2024-05-13 13:31 Chuck Lever III
2024-04-29 13:43 Chuck Lever
2024-04-15 14:06 Chuck Lever
2024-04-09 13:49 Chuck Lever
2024-04-01 14:22 Chuck Lever
2024-03-25 15:26 Chuck Lever III
2024-03-18 13:31 Chuck Lever
2024-03-11 14:08 Chuck Lever
2024-02-26 14:21 Chuck Lever
2024-02-27 5:57 ` Dan Shelton
2024-02-27 14:39 ` Chuck Lever
2024-03-04 13:41 ` Chuck Lever
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=ZjuBjMsY/ZpRjPk1@tissot.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=amir73il@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.