From: Trond Myklebust <trondmy@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Chuck Lever <chuck.lever@oracle.com>, linux-nfs@vger.kernel.org
Subject: [PATCH 0/6] Improve performance of containerised knfsd
Date: Tue, 10 Dec 2019 15:27:29 -0500 [thread overview]
Message-ID: <20191210202735.304477-1-trond.myklebust@hammerspace.com> (raw)
The following patches fix up the garbage collection for the knfsd file
cache, to make the behaviour under load be more predictable.
It also separates out the garbage collectors for knfsd instances running
under different containers to ensure that a close() or fput() of a file
in one container that hangs or is slow won't gum up the system for
all the other containers.
Trond Myklebust (6):
nfsd: fix filecache lookup
nfsd: cleanup nfsd_file_lru_dispose()
nfsd: Containerise filecache laundrette
nfsd: Remove unused constant NFSD_FILE_LRU_RESCAN
nfsd: Schedule the laundrette regularly irrespective of file errors
nfsd: Reduce the number of calls to nfsd_file_gc()
fs/nfsd/filecache.c | 285 ++++++++++++++++++++++++++++++++++----------
fs/nfsd/filecache.h | 2 +
fs/nfsd/nfssvc.c | 9 +-
3 files changed, 230 insertions(+), 66 deletions(-)
--
2.23.0
next reply other threads:[~2019-12-10 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 20:27 Trond Myklebust [this message]
2019-12-10 20:27 ` [PATCH 1/6] nfsd: fix filecache lookup Trond Myklebust
2019-12-10 20:27 ` [PATCH 2/6] nfsd: cleanup nfsd_file_lru_dispose() Trond Myklebust
2019-12-10 20:27 ` [PATCH 3/6] nfsd: Containerise filecache laundrette Trond Myklebust
2019-12-10 20:27 ` [PATCH 4/6] nfsd: Remove unused constant NFSD_FILE_LRU_RESCAN Trond Myklebust
2019-12-10 20:27 ` [PATCH 5/6] nfsd: Schedule the laundrette regularly irrespective of file errors Trond Myklebust
2019-12-10 20:27 ` [PATCH 6/6] nfsd: Reduce the number of calls to nfsd_file_gc() Trond Myklebust
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=20191210202735.304477-1-trond.myklebust@hammerspace.com \
--to=trondmy@gmail.com \
--cc=bfields@fieldses.org \
--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 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.