From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>, clm@fb.com
Subject: [PULL] [PATCH 0/6] B-tree key space extensions
Date: Thu, 11 Feb 2016 18:23:25 +0100 [thread overview]
Message-ID: <cover.1455209994.git.dsterba@suse.com> (raw)
Hi,
this patchset renames some existing key types and gives them a more generalized
meaning (backward compatible). This is motivated by requirements of b-tree
extensions by various patchsets, eg. the deduplication.
The new key type added there BTRFS_DEDUP_STATUS_ITEM_KEY does not use the
objectid or offset members and maps to a single structure. This is very similar
to the balance status item.
The idea is to allow for extensions without key type exhaustion. Obviously we have
to use new values when the offset and objectid are used.
This patchset introduces two types of persistent items to store status data:
* temporary - eg. exists to store state of a running operation like balance
* permanent - eg. exists if a feature is used
The increased variability of the key type will require more parsing, but will
give more flexibility to developers of new features.
The changes are just renames, there's only one user of each type, so no
backward compatibility concerns.
Please consider for 4.6.
----------------------------------------------------------------
The following changes since commit 388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95:
Linux 4.5-rc3 (2016-02-07 15:38:30 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git dev/rename-keys
for you to fetch changes up to 9f07e1d76eaeeddedcf9651395b4a8f870df31f0:
btrfs: teach print_leaf about temporary item subtypes (2016-02-11 16:15:43 +0100)
----------------------------------------------------------------
David Sterba (6):
btrfs: introduce key type for persistent temporary items
btrfs: switch balance item to the temporary item key
btrfs: introduce key type for persistent permanent items
btrfs: switch dev stats item to the permanent item key
btrfs: teach print_leaf about permanent item subtypes
btrfs: teach print_leaf about temporary item subtypes
fs/btrfs/ctree.h | 39 ++++++++++++++++++++++++++++++++++++---
fs/btrfs/print-tree.c | 23 +++++++++++++++++++++--
fs/btrfs/volumes.c | 14 +++++++-------
3 files changed, 64 insertions(+), 12 deletions(-)
--
2.7.1
next reply other threads:[~2016-02-11 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 17:23 David Sterba [this message]
2016-02-11 17:23 ` [PATCH 1/6] btrfs: introduce key type for persistent temporary items David Sterba
2016-02-11 17:23 ` [PATCH 2/6] btrfs: switch balance item to the temporary item key David Sterba
2016-02-11 17:23 ` [PATCH 3/6] btrfs: introduce key type for persistent permanent items David Sterba
2016-02-11 17:23 ` [PATCH 4/6] btrfs: switch dev stats item to the permanent item key David Sterba
2016-02-11 17:23 ` [PATCH 5/6] btrfs: teach print_leaf about permanent item subtypes David Sterba
2016-02-11 17:23 ` [PATCH 6/6] btrfs: teach print_leaf about temporary " 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=cover.1455209994.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=clm@fb.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).