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/6] btrfs-progs: print-tree: Minor enhancement along with --bfs/--dfs options
Date: Fri, 28 Sep 2018 10:04:40 +0800	[thread overview]
Message-ID: <20180928020446.21467-1-wqu@suse.com> (raw)

This patchset can be fetched from github:
https://github.com/adam900710/btrfs-progs/tree/dump_tree_enhance

The main point of this patchset is to allow "btrfs ins dump-tree" to
print tree blocks in breadth-first order when level is higher than 2.

The 1st patch is just a minor cleanup, to remove some unused and
meaningless output.

The 2nd patch does a root<->fs_info cleanup, provides the basis for
later btrfs_next_sibling_tree_block().

The 3rd patch implements a new function, btrfs_next_sibling_tree_block()
to find next sibling tree block, other than leaf.

The 4th patch implements BFS as bfs_print_children().

The BFS search itself is implemented using path along with
 path::lowest_level and btrfs_next_sibling_tree_block() to iterate all
sibling tree blocks in a level.

The 5th patch adds --bfs/--dfs options for dump-tree.

The final patch changes @follow type from int to bool.

Changelog:
v2:
  Make bfs/dfs selectable by adding --bfs and --dfs options.
  Still keep dfs as default (although I really don't see any
  compatibility problem)
  Add a new patch to change @follow type.

Qu Wenruo (6):
  btrfs-progs: print-tree: Skip deprecated blockptr / nodesize output
  btrfs-progs: Replace root parameter using fs_info for
    reada_for_search()
  btrfs-progs: Introduce function to find next sibling tree block
  btrfs-progs: print-tree: Introduce breadth-first search
  btrfs-progs: print-tree: Introduce --bfs and --dfs options
  btrfs-progs: print-tree: Use bool for @follow

 Documentation/btrfs-inspect-internal.asciidoc |   4 +
 cmds-inspect-dump-tree.c                      |  31 ++--
 cmds-restore.c                                |   4 +-
 ctree.c                                       |  25 +--
 ctree.h                                       |  19 ++-
 print-tree.c                                  | 146 ++++++++++++++----
 print-tree.h                                  |  14 +-
 7 files changed, 188 insertions(+), 55 deletions(-)

-- 
2.19.0


             reply	other threads:[~2018-09-28  2:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-28  2:04 Qu Wenruo [this message]
2018-09-28  2:04 ` [PATCH v2 1/6] btrfs-progs: print-tree: Skip deprecated blockptr / nodesize output Qu Wenruo
2018-09-28  2:04 ` [PATCH v2 2/6] btrfs-progs: Replace root parameter using fs_info for reada_for_search() Qu Wenruo
2018-09-28  2:04 ` [PATCH v2 3/6] btrfs-progs: Introduce function to find next sibling tree block Qu Wenruo
2018-09-28  2:04 ` [PATCH v2 4/6] btrfs-progs: print-tree: Introduce breadth-first search Qu Wenruo
2018-09-28  2:04 ` [PATCH v2 5/6] btrfs-progs: print-tree: Introduce --bfs and --dfs options Qu Wenruo
2018-09-28  2:04 ` [PATCH v2 6/6] btrfs-progs: print-tree: Use bool for @follow Qu Wenruo
2018-10-25 16:03 ` [PATCH v2 0/6] btrfs-progs: print-tree: Minor enhancement along with --bfs/--dfs options 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=20180928020446.21467-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).