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: [PATCH v2 0/2] btrfs: btrfs_dec_test_*_ordered_extent() refactor
Date: Tue, 22 Dec 2020 13:59:22 +0800	[thread overview]
Message-ID: <20201222055924.64724-1-wqu@suse.com> (raw)

This small patchset is btrfs_dec_test_*_ordered_extent() refactor during
subpage RW support development.

This is mostly to make btrfs_dev_test_* functions more human readable
and prepare it for calling btrfs_dec_test_first_ordered_extent() in
btrfs_writepage_endio_finish_ordered() where we can have one or more
ordered extents for one bvec.

The first patch is a very safe width reduction, where there is only one
assginment. Thus it should be very safe and won't be involved in other
call sites.

Changelog:
v2:
- Remove the width reduction in the 2nd patch
  The u64->u32 width reduction has too many parts involved, it's really
  hard to do it cleanly just in one patch.
  Remove the width reduction and focus on the existing refactors.

Qu Wenruo (2):
  btrfs: make btrfs_dio_private::bytes to be u32
  btrfs: refactor btrfs_dec_test_* functions for ordered extents

 fs/btrfs/btrfs_inode.h  |  2 +-
 fs/btrfs/inode.c        |  5 +--
 fs/btrfs/ordered-data.c | 99 ++++++++++++++++++++++-------------------
 fs/btrfs/ordered-data.h | 10 ++---
 4 files changed, 60 insertions(+), 56 deletions(-)

-- 
2.29.2


             reply	other threads:[~2020-12-22  6:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22  5:59 Qu Wenruo [this message]
2020-12-22  5:59 ` [PATCH v2 1/2] btrfs: make btrfs_dio_private::bytes to be u32 Qu Wenruo
2020-12-22  5:59 ` [PATCH v2 2/2] btrfs: refactor btrfs_dec_test_* functions for ordered extents Qu Wenruo
2021-01-12 14:29 ` [PATCH v2 0/2] btrfs: btrfs_dec_test_*_ordered_extent() refactor David Sterba

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=20201222055924.64724-1-wqu@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).