Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>, linux-nfs@vger.kernel.org
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH 0/4] Socket creation observability
Date: Mon, 15 May 2023 12:56:54 -0400	[thread overview]
Message-ID: <cad818127d6df4ebcc6e837def684ad381de83fe.camel@kernel.org> (raw)
In-Reply-To: <168415745478.9504.1882537002036193828.stgit@manet.1015granger.net>

On Mon, 2023-05-15 at 09:32 -0400, Chuck Lever wrote:
> This series updates observability around socket creation and
> destruction to help troubleshoot issues such as:
> 
> https://lore.kernel.org/linux-nfs/65AFD2EF-E5D3-4461-B23A-D294486D5F65@oracle.com/T/#t
> 
> I plan to apply these to nfsd-next.
> 
> ---
> 
> Chuck Lever (4):
>       SUNRPC: Fix an incorrect comment
>       SUNRPC: Remove dprintk() in svc_handle_xprt()
>       SUNRPC: Improve observability in svc_tcp_accept()
>       SUNRPC: Trace struct svc_sock lifetime events
> 
> 
>  include/trace/events/sunrpc.h | 39 ++++++++++++++++++++++++-----------
>  net/sunrpc/svc_xprt.c         |  3 ---
>  net/sunrpc/svcsock.c          | 15 ++++++--------
>  3 files changed, 33 insertions(+), 24 deletions(-)
> 
> --
> Chuck Lever
> 

These all look fine to me. I had one nit about a conditional tracepoint,
but your call on whether you want to respin it that way.

Reviewed-by: Jeff Layton <jlayton@kernel.org>

  parent reply	other threads:[~2023-05-15 16:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 13:32 [PATCH 0/4] Socket creation observability Chuck Lever
2023-05-15 13:32 ` [PATCH 1/4] SUNRPC: Fix an incorrect comment Chuck Lever
2023-05-15 13:32 ` [PATCH 2/4] SUNRPC: Remove dprintk() in svc_handle_xprt() Chuck Lever
2023-05-15 13:32 ` [PATCH 3/4] SUNRPC: Improve observability in svc_tcp_accept() Chuck Lever
2023-05-15 16:54   ` Jeff Layton
2023-05-15 17:07     ` Chuck Lever III
2023-05-15 13:33 ` [PATCH 4/4] SUNRPC: Trace struct svc_sock lifetime events Chuck Lever
2023-05-15 16:56 ` Jeff Layton [this message]
2023-05-15 18:10   ` [PATCH 0/4] Socket creation observability Chuck Lever III

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=cad818127d6df4ebcc6e837def684ad381de83fe.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=cel@kernel.org \
    --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