From: Paulo Alcantara <pc@manguebit.com>
To: David Howells <dhowells@redhat.com>,
Steve French <stfrench@microsoft.com>
Cc: dhowells@redhat.com, Jeff Layton <jlayton@kernel.org>,
linux-cifs@vger.kernel.org, netfs@lists.linux.dev,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cifs: Make the write_{enter,done,err} tracepoints display netfs info
Date: Thu, 19 Sep 2024 13:01:10 -0300 [thread overview]
Message-ID: <31d3465bbb306b7390dd7be15e174671@manguebit.com> (raw)
In-Reply-To: <2390624.1726687464@warthog.procyon.org.uk>
David Howells <dhowells@redhat.com> writes:
> Make the write RPC tracepoints use the same trace macro complexes as the
> read tracepoints and display the netfs request and subrequest IDs where
> available (see commit 519be989717c "cifs: Add a tracepoint to track credits
> involved in R/W requests").
>
> Signed-off-by: David Howells <dhowells@redhat.com>
> cc: Steve French <stfrench@microsoft.com>
> cc: Paulo Alcantara (Red Hat) <pc@manguebit.com>
> cc: Jeff Layton <jlayton@kernel.org>
> cc: linux-cifs@vger.kernel.org
> cc: netfs@lists.linux.dev
> cc: linux-fsdevel@vger.kernel.org
> ---
> fs/smb/client/smb2pdu.c | 22 +++++++++++++++-------
> fs/smb/client/trace.h | 6 +++---
> 2 files changed, 18 insertions(+), 10 deletions(-)
Reviewed-by: Paulo Alcantara (Red Hat) <pc@manguebit.com>
next prev parent reply other threads:[~2024-09-19 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 19:24 [PATCH] cifs: Make the write_{enter,done,err} tracepoints display netfs info David Howells
2024-09-19 16:01 ` Paulo Alcantara [this message]
2024-09-23 22:20 ` Steve French
2024-09-23 22:41 ` Steve French
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=31d3465bbb306b7390dd7be15e174671@manguebit.com \
--to=pc@manguebit.com \
--cc=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfs@lists.linux.dev \
--cc=stfrench@microsoft.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