public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Gomez <da.gomez@kernel.org>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>,
	linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: djwong@kernel.org, john.g.garry@oracle.com, willy@infradead.org,
	hch@lst.de, ritesh.list@gmail.com, jack@suse.cz,
	Luis Chamberlain <mcgrof@kernel.org>,
	dgc@kernel.org, tytso@mit.edu, p.raghav@samsung.com,
	andres@anarazel.de, brauner@kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	pankaj.raghav@linux.dev, p.raghav@samsung.com,
	Daniel Gomez <da.gomez@samsung.com>
Subject: Re: [RFC PATCH v2 0/5] Add buffered write-through support to iomap & xfs
Date: Mon, 4 May 2026 09:54:49 +0200	[thread overview]
Message-ID: <d5d99db2-9d34-4caf-bcc8-c4a3af561901@kernel.org> (raw)
In-Reply-To: <cover.1775658795.git.ojaswin@linux.ibm.com>

On 08/04/2026 20.45, Ojaswin Mujoo wrote:
> Hi all,
> 
> This is the v2 RFC to add buffered writethrough support to iomap and
> xfs. The changes made are mostly to get the writethrough implementation
> more inline with how dio handles writes. 
> 
> 

I gave these series a run with kdevops and fstests using the following
profiles: xfs-crc-logdev, xfs-crc, xfs-reflink-logdev, xfs-reflink.

Note that I applied all patches on top of v7.1-rc1 and xfstest-dev
patches from Ojaswin have been rebased on latest master [1].

Link:
https://github.com/dagomez137/xfstests-dev/tree/iomap-buf-writethrough2 [1].

In general, some of the results here seem flaky. But let me know what
you think. I'll try to confirm the possible regressions with another
full run.


Summary per profile:

* xfs-crc-logdev: no regressions or fixes found
* xfs-crc:
  * generic/753 fixed. This test failed on 7.1.0-rc1 run but succeeded
on 7.1.0-rc1-00005-gc6a39600d3c3.
* xfs-reflink-logdev:
  * generic/415 failed on 7.1.0-rc1-00005-gc6a39600d3c3. I tried to
replicate the issue by just running generic/415 (not the entire test
suite), and I couldn't replicate it.
* xfs-reflink:
  * generic/457 failed on 7.1.0-rc1-00005-gc6a39600d3c3.
  * generic/561 failed on 7.1.0-rc1 but not on
7.1.0-rc1-00005-gc6a39600d3c3.


Here the full report list for each A/B profile test run:


http://htmlpreview.github.io/?https://github.com/dagomez137/kdevops-results-archive-wt/blob/main/workflows/fstests/results/r0001/fstests-report-7.1.0-rc1-vs-7.1.0-rc1-00005-gc6a39600d3c3-r0001-qsu-xfs-crc-logdev.html


http://htmlpreview.github.io/?https://github.com/dagomez137/kdevops-results-archive-wt/blob/main/workflows/fstests/results/r0001/fstests-report-7.1.0-rc1-vs-7.1.0-rc1-00005-gc6a39600d3c3-r0001-qsu-xfs-crc.html


http://htmlpreview.github.io/?https://github.com/dagomez137/kdevops-results-archive-wt/blob/main/workflows/fstests/results/r0001/fstests-report-7.1.0-rc1-vs-7.1.0-rc1-00005-gc6a39600d3c3-r0001-qsu-xfs-reflink-logdev.html


http://htmlpreview.github.io/?https://github.com/dagomez137/kdevops-results-archive-wt/blob/main/workflows/fstests/results/r0001/fstests-report-7.1.0-rc1-vs-7.1.0-rc1-00005-gc6a39600d3c3-r0001-qsu-xfs-reflink.html


      parent reply	other threads:[~2026-05-04  7:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08 18:45 [RFC PATCH v2 0/5] Add buffered write-through support to iomap & xfs Ojaswin Mujoo
2026-04-08 18:45 ` [RFC PATCH v2 1/5] mm: Refactor folio_clear_dirty_for_io() Ojaswin Mujoo
2026-04-15  6:14   ` Christoph Hellwig
2026-04-23 10:12     ` Ojaswin Mujoo
2026-04-08 18:45 ` [RFC PATCH v2 2/5] iomap: Add initial support for buffered RWF_WRITETHROUGH Ojaswin Mujoo
2026-04-16 12:05   ` Jan Kara
2026-04-16 12:34   ` Jan Kara
2026-04-17 19:42     ` Ojaswin Mujoo
2026-04-20 11:28       ` Jan Kara
2026-04-21 18:07         ` Ojaswin Mujoo
2026-04-22 10:00           ` Jan Kara
2026-04-23 10:08             ` Ojaswin Mujoo
2026-04-17  4:13   ` Pankaj Raghav (Samsung)
2026-04-18  7:33     ` Ojaswin Mujoo
2026-04-20 11:56   ` Pankaj Raghav (Samsung)
2026-04-21 18:15     ` Ojaswin Mujoo
2026-04-22  6:19       ` Pankaj Raghav
2026-04-22  6:40         ` Ritesh Harjani
2026-04-08 18:45 ` [RFC PATCH v2 3/5] xfs: Add RWF_WRITETHROUGH support to xfs Ojaswin Mujoo
2026-04-08 18:45 ` [RFC PATCH v2 4/5] iomap: Add aio support to RWF_WRITETHROUGH Ojaswin Mujoo
2026-04-08 18:45 ` [RFC PATCH v2 5/5] iomap: Add DSYNC support to writethrough Ojaswin Mujoo
2026-04-17  3:54 ` [RFC PATCH v2 0/5] Add buffered write-through support to iomap & xfs Pankaj Raghav (Samsung)
2026-04-18  7:26   ` Ojaswin Mujoo
2026-04-23 12:25 ` Pankaj Raghav (Samsung)
2026-04-23 23:53   ` Ojaswin Mujoo
2026-04-24  0:17     ` Ritesh Harjani
2026-04-24 10:44       ` Pankaj Raghav
2026-04-24  0:09   ` Ritesh Harjani
2026-05-04  7:54 ` Daniel Gomez [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=d5d99db2-9d34-4caf-bcc8-c4a3af561901@kernel.org \
    --to=da.gomez@kernel.org \
    --cc=andres@anarazel.de \
    --cc=brauner@kernel.org \
    --cc=da.gomez@samsung.com \
    --cc=dgc@kernel.org \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=john.g.garry@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=ojaswin@linux.ibm.com \
    --cc=p.raghav@samsung.com \
    --cc=pankaj.raghav@linux.dev \
    --cc=ritesh.list@gmail.com \
    --cc=tytso@mit.edu \
    --cc=willy@infradead.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