linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>, Neil Brown <neilb@suse.de>,
	 Olga Kornievskaia <kolga@netapp.com>,
	Dai Ngo <Dai.Ngo@oracle.com>,  Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Jeff Layton <jlayton@kernel.org>,
	Jeff Layton <jlayton@kernel.org>
Subject: [PATCH 0/3] nfsd: tracepoint cleanups and additions
Date: Fri, 05 Apr 2024 14:40:48 -0400	[thread overview]
Message-ID: <20240405-nfsd-fixes-v1-0-e017bfe9a783@kernel.org> (raw)

First a patch to remove a few newlines from existing tracepoint string
formats, and then a couple of new tracepoints to instrument some of the
activity around CREATE_SESSION and client expiry. Probably reasonable
for v6.10.

Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
Jeff Layton (3):
      nfsd: drop extraneous newline from nfsd tracepoints
      nfsd: new tracepoint for check_slot_seqid
      nfsd: add tracepoint in mark_client_expired_locked

 fs/nfsd/nfs4state.c | 18 +++++++++------
 fs/nfsd/trace.h     | 64 ++++++++++++++++++++++++++++++++++++++++++++++++++---
 2 files changed, 72 insertions(+), 10 deletions(-)
---
base-commit: 10396f4df8b75ff6ab0aa2cd74296565466f2c8d
change-id: 20240405-nfsd-fixes-adc4524ae2bf

Best regards,
-- 
Jeff Layton <jlayton@kernel.org>


             reply	other threads:[~2024-04-05 18:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 18:40 Jeff Layton [this message]
2024-04-05 18:40 ` [PATCH 1/3] nfsd: drop extraneous newline from nfsd tracepoints Jeff Layton
2024-04-05 18:40 ` [PATCH 2/3] nfsd: new tracepoint for check_slot_seqid Jeff Layton
2024-04-05 19:03   ` Chuck Lever
2024-04-05 19:08     ` Jeff Layton
2024-04-05 18:40 ` [PATCH 3/3] nfsd: add tracepoint in mark_client_expired_locked Jeff Layton

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=20240405-nfsd-fixes-v1-0-e017bfe9a783@kernel.org \
    --to=jlayton@kernel.org \
    --cc=Dai.Ngo@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=kolga@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=tom@talpey.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 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).