public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: cem@kernel.org
To: linux-xfs@vger.kernel.org
Cc: hch@lst.de, dlemoal@kernel.org
Subject: [PATCH v2 0/4] Zoned device cleanups
Date: Tue, 10 Mar 2026 18:36:45 +0100	[thread overview]
Message-ID: <20260310173709.457047-1-cem@kernel.org> (raw)

From: Carlos Maiolino <cem@kernel.org>

This is the V2 of this series, which implement changes suggested by
Damien and Christoph on the V1.

Only changes are on patches 1 and 2.

Original cover follows:

These patches initially were part from an attempt to implement atomic
writes for zoned devices.

Due to unforeseen circumstances, we can't implement it, at least for now
without restructuring a big part of the code.

Christoph though suggested those cleanups were good enough to be sent
even without proceeding with the implementation.


Carlos Maiolino (4):
  xfs: factor out isize updates from xfs_dio_write_end_io
  xfs: factor out xfs_dio_write_zoned_end_io
  xfs: factor out xfs_zone_inc_written
  xfs: opencode xfs_zone_record_blocks

 fs/xfs/xfs_file.c       | 95 ++++++++++++++++++++++++++++++-----------
 fs/xfs/xfs_zone_alloc.c | 32 ++++++--------
 2 files changed, 82 insertions(+), 45 deletions(-)

Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
-- 
2.53.0

             reply	other threads:[~2026-03-10 17:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 17:36 cem [this message]
2026-03-10 17:36 ` [PATCH v2 1/4] xfs: factor out isize updates from xfs_dio_write_end_io cem
2026-03-11  7:03   ` Damien Le Moal
2026-03-12  6:52   ` Christoph Hellwig
2026-03-10 17:36 ` [PATCH v2 2/4] xfs: factor out xfs_dio_write_zoned_end_io cem
2026-03-11  7:03   ` Damien Le Moal
2026-03-10 17:36 ` [PATCH v2 3/4] xfs: factor out xfs_zone_inc_written cem
2026-03-10 17:36 ` [PATCH v2 4/4] xfs: opencode xfs_zone_record_blocks cem
2026-03-18  8:14   ` Christoph Hellwig
2026-03-18  8:33     ` Carlos Maiolino
2026-03-12  8:37 ` [PATCH v2 0/4] Zoned device cleanups Carlos Maiolino

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=20260310173709.457047-1-cem@kernel.org \
    --to=cem@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@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