All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: linux-nfs@vger.kernel.org, netdev@vger.kernel.org
Cc: david@fromorbit.com, jlayton@redhat.com, tgraf@suug.ch
Subject: [PATCH v3 02/32] NFSD: Report filecache LRU size
Date: Fri, 08 Jul 2022 14:23:52 -0400	[thread overview]
Message-ID: <165730463235.28142.14209014620135692603.stgit@klimt.1015granger.net> (raw)
In-Reply-To: <165730437087.28142.6731645688073512500.stgit@klimt.1015granger.net>

Surface the NFSD filecache's LRU list length to help field
troubleshooters monitor filecache issues.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
 fs/nfsd/filecache.c |    4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/fs/nfsd/filecache.c b/fs/nfsd/filecache.c
index 9cb2d590c036..a0234d194ec1 100644
--- a/fs/nfsd/filecache.c
+++ b/fs/nfsd/filecache.c
@@ -1068,7 +1068,7 @@ nfsd_file_create(struct svc_rqst *rqstp, struct svc_fh *fhp,
 static int nfsd_file_cache_stats_show(struct seq_file *m, void *v)
 {
 	unsigned int i, count = 0, longest = 0;
-	unsigned long hits = 0;
+	unsigned long lru = 0, hits = 0;
 
 	/*
 	 * No need for spinlocks here since we're not terribly interested in
@@ -1081,6 +1081,7 @@ static int nfsd_file_cache_stats_show(struct seq_file *m, void *v)
 			count += nfsd_file_hashtbl[i].nfb_count;
 			longest = max(longest, nfsd_file_hashtbl[i].nfb_count);
 		}
+		lru = list_lru_count(&nfsd_file_lru);
 	}
 	mutex_unlock(&nfsd_mutex);
 
@@ -1089,6 +1090,7 @@ static int nfsd_file_cache_stats_show(struct seq_file *m, void *v)
 
 	seq_printf(m, "total entries: %u\n", count);
 	seq_printf(m, "longest chain: %u\n", longest);
+	seq_printf(m, "lru entries:   %lu\n", lru);
 	seq_printf(m, "cache hits:    %lu\n", hits);
 	return 0;
 }



  parent reply	other threads:[~2022-07-08 18:24 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 18:23 [PATCH v3 00/32] Overhaul NFSD filecache Chuck Lever
2022-07-08 18:23 ` [PATCH v3 01/32] NFSD: Demote a WARN to a pr_warn() Chuck Lever
2022-07-08 18:23 ` Chuck Lever [this message]
2022-07-08 18:23 ` [PATCH v3 03/32] NFSD: Report count of calls to nfsd_file_acquire() Chuck Lever
2022-07-08 18:24 ` [PATCH v3 04/32] NFSD: Report count of freed filecache items Chuck Lever
2022-07-08 18:24 ` [PATCH v3 05/32] NFSD: Report average age of " Chuck Lever
2022-07-08 18:24 ` [PATCH v3 06/32] NFSD: Add nfsd_file_lru_dispose_list() helper Chuck Lever
2022-07-08 18:24 ` [PATCH v3 07/32] NFSD: Refactor nfsd_file_gc() Chuck Lever
2022-07-08 18:24 ` [PATCH v3 08/32] NFSD: Refactor nfsd_file_lru_scan() Chuck Lever
2022-07-08 18:24 ` [PATCH v3 09/32] NFSD: Report the number of items evicted by the LRU walk Chuck Lever
2022-07-08 18:24 ` [PATCH v3 10/32] NFSD: Record number of flush calls Chuck Lever
2022-07-08 18:24 ` [PATCH v3 11/32] NFSD: Zero counters when the filecache is re-initialized Chuck Lever
2022-07-08 18:24 ` [PATCH v3 12/32] NFSD: Hook up the filecache stat file Chuck Lever
2022-07-08 19:16   ` Jeff Layton
2022-07-08 18:25 ` [PATCH v3 13/32] NFSD: WARN when freeing an item still linked via nf_lru Chuck Lever
2022-07-08 18:25 ` [PATCH v3 14/32] NFSD: Trace filecache LRU activity Chuck Lever
2022-07-08 18:25 ` [PATCH v3 15/32] NFSD: Leave open files out of the filecache LRU Chuck Lever
2022-07-08 19:29   ` Jeff Layton
2022-07-09 20:45     ` Chuck Lever III
2022-07-11 11:39       ` Jeff Layton
2022-07-08 18:25 ` [PATCH v3 16/32] NFSD: Fix the filecache LRU shrinker Chuck Lever
2022-07-08 19:37   ` Jeff Layton
2022-07-08 18:25 ` [PATCH v3 17/32] NFSD: Never call nfsd_file_gc() in foreground paths Chuck Lever
2022-07-08 19:43   ` Jeff Layton
2022-07-08 19:45     ` Chuck Lever III
2022-07-08 18:25 ` [PATCH v3 18/32] NFSD: No longer record nf_hashval in the trace log Chuck Lever
2022-07-08 18:25 ` [PATCH v3 19/32] NFSD: Remove lockdep assertion from unhash_and_release_locked() Chuck Lever
2022-07-08 18:25 ` [PATCH v3 20/32] NFSD: nfsd_file_unhash can compute hashval from nf->nf_inode Chuck Lever
2022-07-08 18:25 ` [PATCH v3 21/32] NFSD: Refactor __nfsd_file_close_inode() Chuck Lever
2022-07-08 18:26 ` [PATCH v3 22/32] NFSD: nfsd_file_hash_remove can compute hashval Chuck Lever
2022-07-08 18:26 ` [PATCH v3 23/32] NFSD: Remove nfsd_file::nf_hashval Chuck Lever
2022-07-08 18:26 ` [PATCH v3 24/32] NFSD: Replace the "init once" mechanism Chuck Lever
2022-07-08 18:26 ` [PATCH v3 25/32] NFSD: Set up an rhashtable for the filecache Chuck Lever
2022-07-08 18:26 ` [PATCH v3 26/32] NFSD: Convert the filecache to use rhashtable Chuck Lever
2022-07-08 18:26 ` [PATCH v3 27/32] NFSD: Clean up unused code after rhashtable conversion Chuck Lever
2022-07-08 18:26 ` [PATCH v3 28/32] NFSD: Separate tracepoints for acquire and create Chuck Lever
2022-07-08 18:26 ` [PATCH v3 29/32] NFSD: Move nfsd_file_trace_alloc() tracepoint Chuck Lever
2022-07-08 18:26 ` [PATCH v3 30/32] NFSD: Update the nfsd_file_fsnotify_handle_event() tracepoint Chuck Lever
2022-07-08 18:27 ` [PATCH v3 31/32] NFSD: NFSv4 CLOSE should release an nfsd_file immediately Chuck Lever
2022-07-08 18:27 ` [PATCH v3 32/32] NFSD: Ensure nf_inode is never dereferenced Chuck Lever
2022-07-08 20:27 ` [PATCH v3 00/32] Overhaul NFSD filecache Jeff Layton
2022-07-08 20:32   ` 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=165730463235.28142.14209014620135692603.stgit@klimt.1015granger.net \
    --to=chuck.lever@oracle.com \
    --cc=david@fromorbit.com \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tgraf@suug.ch \
    /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.