From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: <linux-nfs@vger.kernel.org>
Subject: [PATCH v4 00/21] NFS add tracepoints (final version)
Date: Wed, 21 Aug 2013 20:23:58 -0400 [thread overview]
Message-ID: <1377131059-40121-1-git-send-email-Trond.Myklebust@netapp.com> (raw)
The following patchset sets up a number of ftrace tracepoints for use
when debugging NFSv4 state operations and NFS performance issues.
Changes in v2:
- Fixed compile bugs
- We need to convert the delegation recall status to a negative number
- Added tracepoints for read/write, pnfs and slot table debugging.
Changes in v3:
- Added tracepoints for generic NFS code
- lookups
- atomic open
- inode cache consistency operations
- internal fsync and data flush operations
- Assorted cleanups and bugfixes
Changes in v4:
- Fix the include file bug
- Add more tracepoints for the generic NFS code
- rename and sillyrename
- generic directory related changes (file create/mknod/mkdir/rmdir/...)
- Add debugging for NFSv4 free stateid events
Trond Myklebust (21):
NFS: refactor code for calculating the crc32 hash of a filehandle
NFS: Add event tracing for generic NFS events
NFS: Pass in lookup flags from nfs_atomic_open to nfs_lookup
NFS: Add event tracing for generic NFS lookups
NFS: Add tracepoints for debugging generic file create events
NFS: Add tracepoints for debugging directory changes
NFS: Add tracepoints for debugging NFS rename and sillyrename issues
NFS: Add tracepoints for debugging NFS hard links
NFSv4: Add tracepoints for debugging state management problems
NFSv4: Add tracepoints for debugging file open
NFSv4: Add tracepoints for debugging file locking
NFSv4: Add tracepoints for debugging lookup/create operations
NFSv4: Add tracepoints for debugging inode manipulations
NFSv4: Add tracepoints for debugging rename
NFSv4: Add tracepoints for debugging delegations
NFSv4: Add tracepoints for debugging the idmapper
NFSv4: Add tracepoints for debugging getattr
NFSv4: Add tracepoints for debugging reads and writes
NFSv4.1: Add tracepoints for debugging layoutget/return/commit
NFSv4.1: Add tracepoints for debugging slot table operations
NFSv4.1: Add tracepoints for debugging test_stateid events
fs/nfs/Makefile | 7 +-
fs/nfs/callback_proc.c | 3 +
fs/nfs/delegation.c | 3 +
fs/nfs/dir.c | 49 +-
fs/nfs/file.c | 5 +
fs/nfs/idmap.c | 5 +
fs/nfs/inode.c | 32 +-
fs/nfs/internal.h | 20 +
fs/nfs/nfs4filelayout.c | 4 +
fs/nfs/nfs4proc.c | 130 ++++--
fs/nfs/nfs4session.h | 10 +
fs/nfs/nfs4trace.c | 17 +
fs/nfs/nfs4trace.h | 1148 +++++++++++++++++++++++++++++++++++++++++++++++
fs/nfs/nfstrace.c | 9 +
fs/nfs/nfstrace.h | 729 ++++++++++++++++++++++++++++++
fs/nfs/pnfs.c | 3 +
fs/nfs/unlink.c | 5 +
fs/nfs/write.c | 15 +-
18 files changed, 2142 insertions(+), 52 deletions(-)
create mode 100644 fs/nfs/nfs4trace.c
create mode 100644 fs/nfs/nfs4trace.h
create mode 100644 fs/nfs/nfstrace.c
create mode 100644 fs/nfs/nfstrace.h
--
1.8.3.1
next reply other threads:[~2013-08-22 0:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 0:23 Trond Myklebust [this message]
2013-08-22 0:23 ` [PATCH v4 01/21] NFS: refactor code for calculating the crc32 hash of a filehandle Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 02/21] NFS: Add event tracing for generic NFS events Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 03/21] NFS: Pass in lookup flags from nfs_atomic_open to nfs_lookup Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 04/21] NFS: Add event tracing for generic NFS lookups Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 05/21] NFS: Add tracepoints for debugging generic file create events Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 06/21] NFS: Add tracepoints for debugging directory changes Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 07/21] NFS: Add tracepoints for debugging NFS rename and sillyrename issues Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 08/21] NFS: Add tracepoints for debugging NFS hard links Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 09/21] NFSv4: Add tracepoints for debugging state management problems Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 10/21] NFSv4: Add tracepoints for debugging file open Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 11/21] NFSv4: Add tracepoints for debugging file locking Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 12/21] NFSv4: Add tracepoints for debugging lookup/create operations Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 13/21] NFSv4: Add tracepoints for debugging inode manipulations Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 14/21] NFSv4: Add tracepoints for debugging rename Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 15/21] NFSv4: Add tracepoints for debugging delegations Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 16/21] NFSv4: Add tracepoints for debugging the idmapper Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 17/21] NFSv4: Add tracepoints for debugging getattr Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 18/21] NFSv4: Add tracepoints for debugging reads and writes Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 19/21] NFSv4.1: Add tracepoints for debugging layoutget/return/commit Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 20/21] NFSv4.1: Add tracepoints for debugging slot table operations Trond Myklebust
2013-08-22 0:24 ` [PATCH v4 21/21] NFSv4.1: Add tracepoints for debugging test_stateid events 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=1377131059-40121-1-git-send-email-Trond.Myklebust@netapp.com \
--to=trond.myklebust@netapp.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 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).