public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: harshad shirwadkar <harshadshirwadkar@gmail.com>
Cc: linux-ext4@vger.kernel.org, jack@suse.cz, harshads@google.com
Subject: Re: [PATCH v8 0/9] Ext4 Fast Commit Performance Patchset
Date: Thu, 1 May 2025 00:14:04 -0400	[thread overview]
Message-ID: <20250501041404.GA205188@mit.edu> (raw)
In-Reply-To: <CAD+ocbzqihJidUkanZLwUfHFNyEs0SO_Tbx4ABr_9W3dRVbArg@mail.gmail.com>

On Wed, Apr 30, 2025 at 11:55:48AM -0700, harshad shirwadkar wrote:
> 
> I tried to run this on my end, and I didn't see the errors that you
> pointed out. Here's my run:
> 
> -------------------- Summary report
> KERNEL:    kernel 6.14.0-rc2-xfstests-perf-gff9ebf4dde0d #31 SMP
> PREEMPT_DYNAMIC Sat Apr 12 19:35:39 UTC 2025 x86_64
> CMDLINE:   -c fast_commit -g auto

I was applying your patches on 6.15-rc3 and this evening I tried
applying them against 6.15-rc2, which has been failing as well.

There's nothing else on the ext4 dev branch yet, but there were a
large number of ext4 patches which landed between 6.14-rc2 and
6.15-rc2.

							- Ted

  reply	other threads:[~2025-05-01  4:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14 16:54 [PATCH v8 0/9] Ext4 Fast Commit Performance Patchset Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 1/9] ext4: convert i_fc_lock to spinlock Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 2/9] ext4: for committing inode, make ext4_fc_track_inode wait Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 3/9] ext4: mark inode dirty before grabbing i_data_sem in ext4_setattr Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 4/9] ext4: rework fast commit commit path Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 5/9] ext4: drop i_fc_updates from inode fc info Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 6/9] ext4: update code documentation Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 7/9] ext4: temporarily elevate commit thread priority Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 8/9] ext4: convert s_fc_lock to mutex type Harshad Shirwadkar
2025-04-14 16:54 ` [PATCH v8 9/9] ext4: hold s_fc_lock while during fast commit Harshad Shirwadkar
2025-04-24 14:59 ` [PATCH v8 0/9] Ext4 Fast Commit Performance Patchset Theodore Ts'o
2025-04-30 18:55   ` harshad shirwadkar
2025-05-01  4:14     ` Theodore Ts'o [this message]
2025-05-01 13:37       ` Theodore Ts'o

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=20250501041404.GA205188@mit.edu \
    --to=tytso@mit.edu \
    --cc=harshads@google.com \
    --cc=harshadshirwadkar@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@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