From: Chuck Lever III <chuck.lever@oracle.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] nfs: clean up some tracepoints in the lookup / revalidate codepaths
Date: Fri, 3 Nov 2023 14:18:06 +0000 [thread overview]
Message-ID: <8EB59F3B-D902-4934-879F-8994C947CB89@oracle.com> (raw)
In-Reply-To: <20231103-nfs-6-8-v1-0-a2aa9021dc1d@kernel.org>
> On Nov 3, 2023, at 3:10 AM, Jeff Layton <jlayton@kernel.org> wrote:
>
> I was looking at a lookupcache issue the other day that turned out to be
> a false alarm. While looking I needed to turn up some tracepoints, and
> found some of the info to be lacking. These patches just do a little
> cleanup to the nfs tracepoints, and flesh them out a bit.
>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
Reviewed-by: Chuck Lever <chuck.lever@oracle.com <mailto:chuck.lever@oracle.com>>
> ---
> Jeff Layton (3):
> nfs: add new tracepoint at nfs4 revalidate entry point
> nfs: rename the nfs_async_rename_done tracepoint
> nfs: print fileid in lookup tracepoints
>
> fs/nfs/dir.c | 2 ++
> fs/nfs/nfstrace.h | 16 +++++++++++-----
> fs/nfs/unlink.c | 2 +-
> 3 files changed, 14 insertions(+), 6 deletions(-)
> ---
> base-commit: 21e80f3841c01aeaf32d7aee7bbc87b3db1aa0c6
> change-id: 20231102-nfs-6-8-7a98e3e480d2
>
> Best regards,
> --
> Jeff Layton <jlayton@kernel.org>
>
--
Chuck Lever
prev parent reply other threads:[~2023-11-03 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 10:10 [PATCH 0/3] nfs: clean up some tracepoints in the lookup / revalidate codepaths Jeff Layton
2023-11-03 10:10 ` [PATCH 1/3] nfs: add new tracepoint at nfs4 revalidate entry point Jeff Layton
2023-11-03 10:10 ` [PATCH 2/3] nfs: rename the nfs_async_rename_done tracepoint Jeff Layton
2023-11-03 10:10 ` [PATCH 3/3] nfs: print fileid in lookup tracepoints Jeff Layton
2023-11-03 14:18 ` Chuck Lever III [this message]
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=8EB59F3B-D902-4934-879F-8994C947CB89@oracle.com \
--to=chuck.lever@oracle.com \
--cc=anna@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
/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.