Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v1 0/6] Deprecate dprintk in svcrdma
Date: Wed, 13 Oct 2021 11:59:26 -0400	[thread overview]
Message-ID: <20211013155926.GC6260@fieldses.org> (raw)
In-Reply-To: <163413628188.6408.17033105928649076434.stgit@bazille.1015granger.net>

On Wed, Oct 13, 2021 at 10:46:49AM -0400, Chuck Lever wrote:
> This patch series moves forward with the removal of dprintk in
> SUNRPC in favor of tracepoints. This is the last step for the
> svcrdma component.

Makes sense to me.

I would like some (very short) documentation, somewhere.  Partly just
for my sake!  I'm not sure exactly what to recommend to bug reporters.

I guess 

	trace-cmd record -e 'sunrpc:*
	trace-cmd report

would be a rough substitute for "rpcdebug -m rpc -s all"?

Do we have a couple examples of issues that could be diagnosed with
tracepoints?  In the past I don't feel like I've ended up using dprintks
all that much; somehow they're not usually where I need them.  But maybe
that's just me.  And maybe as we put more thought into where tracepoints
should be, they'll get more useful.

Documentation/filesystems/nfs/, or the linux-nfs wiki, could be easy
places to put it.  Though *something* in the man pages would be nice.
At a minimum, a warning in rpcdebug(8) that we're gradually phasing out
dprintks.

--b.

> 
> ---
> 
> Chuck Lever (6):
>       svcrdma: Remove dprintk() call sites in module handlers
>       svcrdma: Remove dprintk call site in svc_rdma_create_xprt()
>       svcrdma: Remove dprintk call site in svc_rdma_parse_connect_private()
>       svcrdma: Remove dprintk call sites during QP creation
>       svcrdma: Remove dprintk call sites during accept
>       svcrdma: Remove include/linux/sunrpc/debug.h
> 
> 
>  net/sunrpc/xprtrdma/svc_rdma.c           |  9 ------
>  net/sunrpc/xprtrdma/svc_rdma_recvfrom.c  |  1 -
>  net/sunrpc/xprtrdma/svc_rdma_sendto.c    |  1 -
>  net/sunrpc/xprtrdma/svc_rdma_transport.c | 37 ++----------------------
>  4 files changed, 3 insertions(+), 45 deletions(-)
> 
> --
> Chuck Lever

  parent reply	other threads:[~2021-10-13 15:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13 14:46 [PATCH v1 0/6] Deprecate dprintk in svcrdma Chuck Lever
2021-10-13 14:46 ` [PATCH v1 1/6] svcrdma: Remove dprintk() call sites in module handlers Chuck Lever
2021-10-13 14:47 ` [PATCH v1 2/6] svcrdma: Remove dprintk call site in svc_rdma_create_xprt() Chuck Lever
2021-10-13 14:47 ` [PATCH v1 3/6] svcrdma: Remove dprintk call site in svc_rdma_parse_connect_private() Chuck Lever
2021-10-13 14:47 ` [PATCH v1 4/6] svcrdma: Remove dprintk call sites during QP creation Chuck Lever
2021-10-13 14:47 ` [PATCH v1 5/6] svcrdma: Remove dprintk call sites during accept Chuck Lever
2021-10-13 14:47 ` [PATCH v1 6/6] svcrdma: Remove include/linux/sunrpc/debug.h Chuck Lever
2021-10-13 15:59 ` J. Bruce Fields [this message]
2021-10-13 16:49   ` [PATCH v1 0/6] Deprecate dprintk in svcrdma Chuck Lever III
2021-10-13 18:35     ` David Wysochanski
2021-10-13 21:03       ` Chuck Lever III
2021-11-03  7:56         ` David Wysochanski

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=20211013155926.GC6260@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@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