From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: REF_COWS bit rework
Date: Wed, 13 May 2020 14:16:09 +0800 [thread overview]
Message-ID: <20200513061611.111807-1-wqu@suse.com> (raw)
This small patchset reworks the REF_COWS bit, by renaming it, and remove
that bit for data relocation root.
The basic idea of such rework is to reduce the confusion caused by the
name REF_COWS.
With the new bit called SHAREABLE, it should be clear that no user can
really create snapshot for data reloc tree, thus its tree blocks
shouldn't be shareable.
This would make data balance for reloc tree a little simpler.
Qu Wenruo (2):
btrfs: Rename BTRFS_ROOT_REF_COWS to BTRFS_ROOT_SHAREABLE
btrfs: Don't set SHAREABLE flag for data reloc tree
fs/btrfs/backref.c | 4 ++--
fs/btrfs/backref.h | 2 +-
fs/btrfs/block-rsv.c | 2 +-
fs/btrfs/ctree.c | 26 +++++++++++++-------------
fs/btrfs/ctree.h | 25 +++++++++++++++++++++++--
fs/btrfs/disk-io.c | 27 ++++++++++++++++++++-------
fs/btrfs/extent-tree.c | 2 +-
fs/btrfs/file.c | 2 +-
fs/btrfs/inode.c | 27 ++++++++++++++++-----------
fs/btrfs/ioctl.c | 2 +-
fs/btrfs/relocation.c | 42 +++++++++++++++++-------------------------
fs/btrfs/transaction.c | 12 ++++++------
fs/btrfs/tree-defrag.c | 2 +-
13 files changed, 103 insertions(+), 72 deletions(-)
--
2.26.2
next reply other threads:[~2020-05-13 6:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 6:16 Qu Wenruo [this message]
2020-05-13 6:16 ` [PATCH 1/2] btrfs: Rename BTRFS_ROOT_REF_COWS to BTRFS_ROOT_SHAREABLE Qu Wenruo
2020-05-13 14:18 ` David Sterba
2020-05-13 6:16 ` [PATCH 2/2] btrfs: Don't set SHAREABLE flag for data reloc tree Qu Wenruo
2020-05-13 6:44 ` Nikolay Borisov
2020-05-13 6:49 ` Qu Wenruo
2020-05-13 13:51 ` David Sterba
2020-05-14 0:01 ` Qu Wenruo
2020-05-13 14:01 ` David Sterba
2020-05-14 0:06 ` Qu Wenruo
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=20200513061611.111807-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.