linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/3] btrfs: btrfs_buffered_write() cleanups
Date: Tue, 12 Nov 2024 17:56:06 +1030	[thread overview]
Message-ID: <69c81dfb-a3d6-4e89-ba2e-66064a62c731@suse.com> (raw)
In-Reply-To: <cover.1731396107.git.wqu@suse.com>



在 2024/11/12 17:53, Qu Wenruo 写道:
> This series is to cleanup btrfs_buffered_write() so that it's more
> aligned to iomap_writer_iter(), and makes later migration a little
> easier.
> 
> All those changes are inside btrfs, and the last 2 should improve the
> readablity, and prepare for the migration (since everything is now done
> inside the loop).

Changelog:
v2:
- Change the migration target from aops->write_begin() to iomap
   Otherwise no code changes


> 
> Qu Wenruo (3):
>    btrfs: make buffered write to respect fatal signals
>    btrfs: cleanup the variables inside btrfs_buffered_write()
>    btrfs: remove the out-of-loop cleanup from btrfs_buffered_write()
> 
>   fs/btrfs/file.c | 90 ++++++++++++++++++++++++++-----------------------
>   1 file changed, 47 insertions(+), 43 deletions(-)
> 


      parent reply	other threads:[~2024-11-12  7:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12  7:23 [PATCH v2 0/3] btrfs: btrfs_buffered_write() cleanups Qu Wenruo
2024-11-12  7:23 ` [PATCH v2 1/3] btrfs: make buffered write to respect fatal signals Qu Wenruo
2024-11-12  7:23 ` [PATCH v2 2/3] btrfs: cleanup the variables inside btrfs_buffered_write() Qu Wenruo
2024-11-12  7:23 ` [PATCH v2 3/3] btrfs: remove the out-of-loop cleanup from btrfs_buffered_write() Qu Wenruo
2024-11-12  7:26 ` Qu Wenruo [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=69c81dfb-a3d6-4e89-ba2e-66064a62c731@suse.com \
    --to=wqu@suse.com \
    --cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).