From: Jeff Layton <jlayton@kernel.org>
To: Trond Myklebust <trondmy@kernel.org>, Anna Schumaker <anna@kernel.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeff Layton <jlayton@kernel.org>
Subject: [PATCH 0/4] nfs: client-side tracepoints for delegations and cache coherency
Date: Tue, 03 Jun 2025 07:42:22 -0400 [thread overview]
Message-ID: <20250603-nfs-tracepoints-v1-0-d2615f3bbe6c@kernel.org> (raw)
These are some tracepoints that I rolled a while back when working on
the client-side pieces of the directory delegation patchset. I think
that these are useful in their own right, even without dir delegations.
Please consider these for v6.17.
Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
Jeff Layton (4):
nfs: add cache_validity to the nfs_inode_event tracepoints
nfs: add a tracepoint to nfs_inode_detach_delegation_locked
nfs: new tracepoint in nfs_delegation_need_return
nfs: new tracepoint in match_stateid operation
fs/nfs/delegation.c | 4 ++
fs/nfs/nfs4proc.c | 4 ++
fs/nfs/nfs4trace.h | 104 ++++++++++++++++++++++++++++++++++++++++++++++++++++
fs/nfs/nfstrace.h | 8 +++-
4 files changed, 118 insertions(+), 2 deletions(-)
---
base-commit: e3e3775392f3f0f3e3044f8c162bf47858e01759
change-id: 20250603-nfs-tracepoints-034454716137
Best regards,
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2025-06-03 11:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 11:42 Jeff Layton [this message]
2025-06-03 11:42 ` [PATCH 1/4] nfs: add cache_validity to the nfs_inode_event tracepoints Jeff Layton
2025-06-03 11:42 ` [PATCH 2/4] nfs: add a tracepoint to nfs_inode_detach_delegation_locked Jeff Layton
2025-06-03 11:42 ` [PATCH 3/4] nfs: new tracepoint in nfs_delegation_need_return Jeff Layton
2025-06-03 11:42 ` [PATCH 4/4] nfs: new tracepoint in match_stateid operation Jeff Layton
2025-06-10 13:04 ` Benjamin Coddington
2025-06-10 13:09 ` Jeff Layton
2025-06-17 18:45 ` Trond Myklebust
2025-06-10 13:05 ` [PATCH 0/4] nfs: client-side tracepoints for delegations and cache coherency Benjamin Coddington
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=20250603-nfs-tracepoints-v1-0-d2615f3bbe6c@kernel.org \
--to=jlayton@kernel.org \
--cc=anna@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).