Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: chuck.lever@oracle.com
Cc: linux-nfs@vger.kernel.org, neilb@suse.de
Subject: [PATCH v6 0/4] nfsd: clean up refcounting in the filecache
Date: Wed,  2 Nov 2022 14:44:46 -0400	[thread overview]
Message-ID: <20221102184450.130397-1-jlayton@kernel.org> (raw)

v6:
- merge the LRU handling fixes into the refcount fixing patches
- call nfsd_file_close_inode from the notifier callbacks, which
  decrements and queues any objects to be freed by the disposal
  workqueue job

Only two main changes in this patchset. I folded two patches together
to avoid a problem that Chuck hit while testing. The other significant
change is to have the notifier callbacks use the disposal workqueue
job instead of freeing things themselves. Those don't need to be done
synchronously.

Jeff Layton (4):
  nfsd: remove the pages_flushed statistic from filecache
  nfsd: reorganize filecache.c
  nfsd: rework refcounting in filecache
  nfsd: fix up the filecache laundrette scheduling

 fs/nfsd/filecache.c | 406 +++++++++++++++++++++++---------------------
 fs/nfsd/filecache.h |   1 +
 fs/nfsd/trace.h     |  11 +-
 3 files changed, 222 insertions(+), 196 deletions(-)

-- 
2.38.1


             reply	other threads:[~2022-11-02 18:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 18:44 Jeff Layton [this message]
2022-11-02 18:44 ` [PATCH v6 1/4] nfsd: remove the pages_flushed statistic from filecache Jeff Layton
2022-11-02 18:44 ` [PATCH v6 2/4] nfsd: reorganize filecache.c Jeff Layton
2022-11-02 18:44 ` [PATCH v6 3/4] nfsd: rework refcounting in filecache Jeff Layton
2022-11-02 18:44 ` [PATCH v6 4/4] nfsd: fix up the filecache laundrette scheduling Jeff Layton
2022-11-03 19:19 ` [PATCH v6 0/4] nfsd: clean up refcounting in the filecache 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=20221102184450.130397-1-jlayton@kernel.org \
    --to=jlayton@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    /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