From: Bruce Fields <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Bill Baker <Bill.Baker@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v2 00/27] NFSD operation monitoring tracepoints
Date: Fri, 25 Sep 2020 10:32:18 -0400 [thread overview]
Message-ID: <20200925143218.GD1096@fieldses.org> (raw)
In-Reply-To: <945A7DE6-909D-4177-852F-F80EF7DFE6B3@oracle.com>
On Fri, Sep 25, 2020 at 09:59:51AM -0400, Chuck Lever wrote:
> Thanks Bruce, for your time, attention, and comments!
>
> > On Sep 24, 2020, at 5:36 PM, J. Bruce Fields <bfields@fieldses.org> wrote:
> >
> > On Mon, Sep 21, 2020 at 02:10:49PM -0400, Chuck Lever wrote:
> >> As I've been working on various server bugs, I've been adding
> >> tracepoints that record NFS operation arguments. Here's an updated
> >> snapshot of this work for your review and comment.
> >>
> >> The idea here is to provide a degree of NFS traffic observability
> >> without needing network capture. Tracepoints are generally lighter-
> >> weight than full network capture, allowing effective capture-time
> >> data reduction:
> >
> > I do wonder when tracepoints seem to duplicate information you could get
> > from network traces, so thanks for taking the time to explain this. It
> > makes sense to me.
> >
> > The patches look fine. The only one I'm I'm on the fence about is the
> > last with the split up of the dispatch functions. I'll ask some
> > questions there....
>
> To be clear to everyone, this series is still "preview". I expect
> more churn in these patches, thus I don't consider the series ready
> to be merged by any stretch.
OK!
One thing I was wondering about: how would you limit tracing to a single
client, say if you wanted to see all DELEGRETURNs from a single client?
I guess you'd probably turn on a tracepoint in the receive code, look
for your client's IP address, then mask the task id to match later
nfs-level tracepoints. Is there enough information in those tracepoints
(including network namespace) to uniquely identify a client?
--b.
> >> - One or a handful of these can be enabled at a time
> >> - Each tracepoint records much less data per operation than capture
> >> - Extra capture-time filtering can reduce data amount even further
> >> - Some of these operations are infrequent enough that their
> >> tracepoint could be enabled persistently without a significant
> >> performance impact (for example, for security auditing)
> >>
> >> The topic branch has been updated as well:
> >>
> >> git://git.linux-nfs.org/projects/cel/cel-2.6.git nfsd-more-tracepoints
> >>
> >>
> >> Changes since RFC:
> >> * s/SPDK/SPDX and corrected the spelling of Christoph's surname
> >> * Fixed a build error noticed by <lkp@intel.com>
> >> * Introduced generic headers for VFS and NFS protocol display macros
> >> * nfsd4_compoundstatus now displays NFS4ERR codes symbolically
> >> * The svc_process tracepoint now displays the RPC procedure symbolically
> >> * NFSD dispatcher now displays procedure names and status codes symbolically
> >> * fh_verify tracepoint tentatively included; it adds a lot of noise, but perhaps not much value
> >> * Cleaned up the remaining PROC() macros in the server code
> >> * Removed trace_printk's that were introduced during the RFC series
> >> * Removed redundant nfsd4_close tracepoint
> >>
> >> ---
> >>
> >> Chuck Lever (27):
> >> NFS: Move generic FS show macros to global header
> >> NFS: Move NFS protocol display macros to global header
> >> NFSD: Add SPDX header for fs/nfsd/trace.c
> >> SUNRPC: Move the svc_xdr_recvfrom() tracepoint
> >> SUNRPC: Add svc_xdr_authenticate tracepoint
> >> lockd: Replace PROC() macro with open code
> >> NFSACL: Replace PROC() macro with open code
> >> SUNRPC: Make trace_svc_process() display the RPC procedure symbolically
> >> NFSD: Clean up the show_nf_may macro
> >> NFSD: Remove extra "0x" in tracepoint format specifier
> >> NFSD: Constify @fh argument of knfsd_fh_hash()
> >> NFSD: Add tracepoint in nfsd_setattr()
> >> NFSD: Add tracepoint for nfsd_access()
> >> NFSD: nfsd_compound_status tracepoint should record XID
> >> NFSD: Add client ID lifetime tracepoints
> >> NFSD: Add tracepoints to report NFSv4 session state
> >> NFSD: Add a tracepoint to report the current filehandle
> >> NFSD: Add GETATTR tracepoint
> >> NFSD: Add tracepoint in nfsd4_stateid_preprocess()
> >> NFSD: Add tracepoint to report arguments to NFSv4 OPEN
> >> NFSD: Add a tracepoint for DELEGRETURN
> >> NFSD: Add a lookup tracepoint
> >> NFSD: Add lock and locku tracepoints
> >> NFSD: Add tracepoints to record the result of TEST_STATEID and FREE_STATEID
> >> NFSD: Rename nfsd_ tracepoints to nfsd4_
> >> NFSD: Add tracepoints in the NFS dispatcher
> >> NFSD: Replace dprintk callsites in fs/nfsd/nfsfh.c
> >>
> >>
> >> fs/lockd/svc4proc.c | 263 +++++++++--
> >> fs/lockd/svcproc.c | 265 +++++++++--
> >> fs/nfs/callback_xdr.c | 2 +
> >> fs/nfs/nfs4trace.h | 387 ++--------------
> >> fs/nfs/nfstrace.h | 113 +----
> >> fs/nfs/pnfs.h | 4 -
> >> fs/nfsd/nfs2acl.c | 79 +++-
> >> fs/nfsd/nfs3acl.c | 54 ++-
> >> fs/nfsd/nfs3proc.c | 25 +
> >> fs/nfsd/nfs4callback.c | 28 +-
> >> fs/nfsd/nfs4layouts.c | 16 +-
> >> fs/nfsd/nfs4proc.c | 43 +-
> >> fs/nfsd/nfs4state.c | 100 ++--
> >> fs/nfsd/nfsd.h | 1 +
> >> fs/nfsd/nfsfh.c | 36 +-
> >> fs/nfsd/nfsfh.h | 7 +-
> >> fs/nfsd/nfsproc.c | 21 +
> >> fs/nfsd/nfssvc.c | 198 +++++---
> >> fs/nfsd/trace.c | 1 +
> >> fs/nfsd/trace.h | 844 ++++++++++++++++++++++++++++++----
> >> fs/nfsd/vfs.c | 18 +-
> >> fs/nfsd/xdr4.h | 3 +-
> >> include/linux/nfs4.h | 4 +
> >> include/linux/sunrpc/svc.h | 1 +
> >> include/trace/events/fs.h | 30 ++
> >> include/trace/events/nfs.h | 511 ++++++++++++++++++++
> >> include/trace/events/sunrpc.h | 33 +-
> >> include/uapi/linux/nfsacl.h | 2 +
> >> net/sunrpc/svc_xprt.c | 4 +-
> >> net/sunrpc/svcauth.c | 5 +-
> >> 30 files changed, 2187 insertions(+), 911 deletions(-)
> >> create mode 100644 include/trace/events/nfs.h
> >>
> >> --
> >> Chuck Lever
>
> --
> Chuck Lever
>
>
next prev parent reply other threads:[~2020-09-25 14:32 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 18:10 [PATCH v2 00/27] NFSD operation monitoring tracepoints Chuck Lever
2020-09-21 18:10 ` [PATCH v2 01/27] NFS: Move generic FS show macros to global header Chuck Lever
2020-09-21 18:11 ` [PATCH v2 02/27] NFS: Move NFS protocol display " Chuck Lever
2020-09-21 18:11 ` [PATCH v2 03/27] NFSD: Add SPDX header for fs/nfsd/trace.c Chuck Lever
2020-09-21 18:11 ` [PATCH v2 04/27] SUNRPC: Move the svc_xdr_recvfrom() tracepoint Chuck Lever
2020-09-21 18:11 ` [PATCH v2 05/27] SUNRPC: Add svc_xdr_authenticate tracepoint Chuck Lever
2020-09-21 18:11 ` [PATCH v2 06/27] lockd: Replace PROC() macro with open code Chuck Lever
2020-09-21 18:11 ` [PATCH v2 07/27] NFSACL: " Chuck Lever
2020-09-21 18:11 ` [PATCH v2 08/27] SUNRPC: Make trace_svc_process() display the RPC procedure symbolically Chuck Lever
2020-09-21 18:11 ` [PATCH v2 09/27] NFSD: Clean up the show_nf_may macro Chuck Lever
2020-09-21 18:11 ` [PATCH v2 10/27] NFSD: Remove extra "0x" in tracepoint format specifier Chuck Lever
2020-09-21 18:11 ` [PATCH v2 11/27] NFSD: Constify @fh argument of knfsd_fh_hash() Chuck Lever
2020-09-21 18:11 ` [PATCH v2 12/27] NFSD: Add tracepoint in nfsd_setattr() Chuck Lever
2020-09-21 18:11 ` [PATCH v2 13/27] NFSD: Add tracepoint for nfsd_access() Chuck Lever
2020-09-21 18:12 ` [PATCH v2 14/27] NFSD: nfsd_compound_status tracepoint should record XID Chuck Lever
2020-09-21 18:12 ` [PATCH v2 15/27] NFSD: Add client ID lifetime tracepoints Chuck Lever
2020-09-21 18:12 ` [PATCH v2 16/27] NFSD: Add tracepoints to report NFSv4 session state Chuck Lever
2020-09-21 18:12 ` [PATCH v2 17/27] NFSD: Add a tracepoint to report the current filehandle Chuck Lever
2020-09-21 18:12 ` [PATCH v2 18/27] NFSD: Add GETATTR tracepoint Chuck Lever
2020-09-21 18:12 ` [PATCH v2 19/27] NFSD: Add tracepoint in nfsd4_stateid_preprocess() Chuck Lever
2020-09-21 18:12 ` [PATCH v2 20/27] NFSD: Add tracepoint to report arguments to NFSv4 OPEN Chuck Lever
2020-09-21 18:12 ` [PATCH v2 21/27] NFSD: Add a tracepoint for DELEGRETURN Chuck Lever
2020-09-21 18:12 ` [PATCH v2 22/27] NFSD: Add a lookup tracepoint Chuck Lever
2020-09-21 18:12 ` [PATCH v2 23/27] NFSD: Add lock and locku tracepoints Chuck Lever
2020-09-21 18:12 ` [PATCH v2 24/27] NFSD: Add tracepoints to record the result of TEST_STATEID and FREE_STATEID Chuck Lever
2020-09-21 18:13 ` [PATCH v2 25/27] NFSD: Rename nfsd_ tracepoints to nfsd4_ Chuck Lever
2020-09-21 18:13 ` [PATCH v2 26/27] NFSD: Add tracepoints in the NFS dispatcher Chuck Lever
2020-09-24 23:45 ` J. Bruce Fields
2020-09-25 13:59 ` Chuck Lever
2020-09-25 14:17 ` Bruce Fields
2020-09-25 14:21 ` Chuck Lever
2020-09-25 14:18 ` Chuck Lever
2020-09-25 14:47 ` Bruce Fields
2020-09-21 18:13 ` [PATCH v2 27/27] NFSD: Replace dprintk callsites in fs/nfsd/nfsfh.c Chuck Lever
2020-09-24 21:36 ` [PATCH v2 00/27] NFSD operation monitoring tracepoints J. Bruce Fields
2020-09-25 13:59 ` Chuck Lever
2020-09-25 14:32 ` Bruce Fields [this message]
2020-09-25 14:36 ` Chuck Lever
2020-09-25 15:00 ` Bruce Fields
2020-09-25 15:05 ` Chuck Lever
2020-09-25 17:04 ` Chuck Lever
2020-09-25 18:37 ` Bruce Fields
2020-09-25 18:41 ` Chuck Lever
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=20200925143218.GD1096@fieldses.org \
--to=bfields@fieldses.org \
--cc=Bill.Baker@oracle.com \
--cc=chuck.lever@oracle.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).