public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 00/12] btrfs: item helper prep work for snapshot_id
Date: Mon,  7 Mar 2022 17:33:19 -0500	[thread overview]
Message-ID: <cover.1646692306.git.josef@toxicpanda.com> (raw)

Hello,

I sent a bunch of patches previously to rework a lot of our helpers in
preparation of adding the snapshot_id to the btrfs_header.  I missed a few
important areas with those patches, so here's the remaining work to make it
easier to expand the size of the btrfs_header.  These are general fixups and
cleanups that don't rely on the extent tree v2 work.  Thanks,

Josef

Josef Bacik (12):
  btrfs: move btrfs_node_key into ctree.h
  btrfs: add a btrfs_node_key_ptr helper, convert the users
  btrfs: introduce *_leaf_data helpers
  btrfs: make BTRFS_LEAF_DATA_OFFSET take an eb arg
  btrfs: pass eb to the node_key_ptr helpers
  btrfs: pass eb to the item_nr_offset helper
  btrfs: add snapshot_id to the btrfs_header and related defs
  btrfs: move the header SETGET funcs
  btrfs: move the super SETGET funcs
  btrfs: move BTRFS_LEAF related definitions below super SETGET funcs
  btrfs: const-ify fs_info for the compat flag handlers
  btrfs: use _offset helpers instead of offsetof in generic_bin_search

 fs/btrfs/ctree.c                | 151 ++++++------
 fs/btrfs/ctree.h                | 411 +++++++++++++++++---------------
 fs/btrfs/extent_io.c            |   6 +-
 fs/btrfs/struct-funcs.c         |   8 -
 fs/btrfs/tree-checker.c         |   4 +-
 fs/btrfs/tree-mod-log.c         |   4 +-
 include/uapi/linux/btrfs_tree.h |   1 +
 7 files changed, 303 insertions(+), 282 deletions(-)

-- 
2.26.3


             reply	other threads:[~2022-03-07 22:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 22:33 Josef Bacik [this message]
2022-03-07 22:33 ` [PATCH 01/12] btrfs: move btrfs_node_key into ctree.h Josef Bacik
2022-03-07 22:33 ` [PATCH 02/12] btrfs: add a btrfs_node_key_ptr helper, convert the users Josef Bacik
2022-03-09 13:48   ` Nikolay Borisov
2022-03-09 13:48     ` Nikolay Borisov
2022-03-07 22:33 ` [PATCH 03/12] btrfs: introduce *_leaf_data helpers Josef Bacik
2022-03-07 22:33 ` [PATCH 04/12] btrfs: make BTRFS_LEAF_DATA_OFFSET take an eb arg Josef Bacik
2022-03-07 22:33 ` [PATCH 05/12] btrfs: pass eb to the node_key_ptr helpers Josef Bacik
2022-03-07 22:33 ` [PATCH 06/12] btrfs: pass eb to the item_nr_offset helper Josef Bacik
2022-03-09 13:55   ` Nikolay Borisov
2022-03-07 22:33 ` [PATCH 07/12] btrfs: add snapshot_id to the btrfs_header and related defs Josef Bacik
2022-03-07 22:33 ` [PATCH 08/12] btrfs: move the header SETGET funcs Josef Bacik
2022-03-07 22:33 ` [PATCH 09/12] btrfs: move the super " Josef Bacik
2022-03-07 22:33 ` [PATCH 10/12] btrfs: move BTRFS_LEAF related definitions below " Josef Bacik
2022-03-07 22:33 ` [PATCH 11/12] btrfs: const-ify fs_info for the compat flag handlers Josef Bacik
2022-03-07 22:33 ` [PATCH 12/12] btrfs: use _offset helpers instead of offsetof in generic_bin_search Josef Bacik
2022-03-09 13:51   ` Nikolay Borisov
2022-03-09 13:57 ` [PATCH 00/12] btrfs: item helper prep work for snapshot_id Nikolay Borisov
2022-03-14 17:12   ` Sweet Tea Dorminy

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.1646692306.git.josef@toxicpanda.com \
    --to=josef@toxicpanda.com \
    --cc=kernel-team@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