linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anna Schumaker <anna.schumaker@oracle.com>
To: Jeff Layton <jlayton@kernel.org>,
	Trond Myklebust <trondmy@kernel.org>,
	Anna Schumaker <anna@kernel.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Benjamin Coddington <bcodding@redhat.com>
Subject: Re: [PATCH 0/5] nfs: more client side tracepoints in write and writeback codepaths
Date: Tue, 2 Sep 2025 13:56:08 -0400	[thread overview]
Message-ID: <b04e9fcc-487b-4071-a0c4-577dbf4cd55f@oracle.com> (raw)
In-Reply-To: <0a01b5bb79b9cc012af310f6be72d8b7b32c18fe.camel@kernel.org>



On 8/29/25 10:45 AM, Jeff Layton wrote:
> On Fri, 2025-08-08 at 07:40 -0400, Jeff Layton wrote:
>> This is a pile of tracepoint additions and cleanups. Most of these I
>> plumbed in while tracking down the recent client-side corruption I've
>> been hunting. Please consider for v6.18.
>>
>> Thanks,
>>
>> Signed-off-by: Jeff Layton <jlayton@kernel.org>
>> ---
>> Jeff Layton (5):
>>       nfs: remove trailing space from tracepoint
>>       nfs: add tracepoints to nfs_file_read() and nfs_file_write()
>>       nfs: new tracepoints around write handling
>>       nfs: more in-depth tracing of writepage events
>>       nfs: add tracepoints to nfs_writepages()
>>
>>  fs/nfs/file.c     |  20 ++++++--
>>  fs/nfs/nfstrace.h | 135 +++++++++++++++++++++++++++++++++++++++++++++++++++++-
>>  fs/nfs/write.c    |  22 +++++++--
>>  3 files changed, 168 insertions(+), 9 deletions(-)
>> ---
>> base-commit: 0919a5b3b11c699d23bc528df5709f2e3213f6a9
>> change-id: 20250807-nfs-tracepoints-f1d84186564d
>>
>> Best regards,
> 
> Ping? I haven't seen a response, or these in linux-next yet. Can we get
> them in soon so they can make v6.18?

Hi Jeff,

They look good to me, and I'm planning on taking them for 6.18.

Anna

> 
> They were pretty helpful for tracking down that pgio fix recently.
> 
> Thanks,


      reply	other threads:[~2025-09-02 17:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-08 11:40 [PATCH 0/5] nfs: more client side tracepoints in write and writeback codepaths Jeff Layton
2025-08-08 11:40 ` [PATCH 1/5] nfs: remove trailing space from tracepoint Jeff Layton
2025-08-11 12:32   ` Jeff Layton
2025-08-08 11:40 ` [PATCH 2/5] nfs: add tracepoints to nfs_file_read() and nfs_file_write() Jeff Layton
2025-08-08 11:40 ` [PATCH 3/5] nfs: new tracepoints around write handling Jeff Layton
2025-08-08 11:40 ` [PATCH 4/5] nfs: more in-depth tracing of writepage events Jeff Layton
2025-08-08 11:40 ` [PATCH 5/5] nfs: add tracepoints to nfs_writepages() Jeff Layton
2025-08-08 12:38 ` [PATCH 0/5] nfs: more client side tracepoints in write and writeback codepaths Benjamin Coddington
2025-08-29 14:45 ` Jeff Layton
2025-09-02 17:56   ` Anna Schumaker [this message]

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=b04e9fcc-487b-4071-a0c4-577dbf4cd55f@oracle.com \
    --to=anna.schumaker@oracle.com \
    --cc=anna@kernel.org \
    --cc=bcodding@redhat.com \
    --cc=jlayton@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@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).