linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Chandan Babu R <chandan.babu@oracle.com>,
	"Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: RFC: in-memory btree simplifications
Date: Wed,  3 Jan 2024 21:38:31 +0100	[thread overview]
Message-ID: <20240103203836.608391-1-hch@lst.de> (raw)

Hi Darrick,

this series has a bunch of simplifications for the xfbtree code I came
up with while reviewing it and trying to understand the logic.

The series is against the djwong-wtf with everything and the kitchen
sink, and will need some heavy rebasing.  As always I'll offer to it
if the changes themselves look good.  I'll probably have a few more
invasive bits in this area when I get further.

Diffstat:
 Documentation/filesystems/xfs-online-fsck-design.rst |    5 
 fs/xfs/libxfs/xfs_bmap.c                             |   27 -
 fs/xfs/libxfs/xfs_bmap_btree.c                       |   14 
 fs/xfs/libxfs/xfs_btree.c                            |   52 +--
 fs/xfs/libxfs/xfs_btree.h                            |   13 
 fs/xfs/libxfs/xfs_btree_mem.h                        |   38 --
 fs/xfs/libxfs/xfs_rmap_btree.c                       |   17 -
 fs/xfs/libxfs/xfs_rmap_btree.h                       |    5 
 fs/xfs/libxfs/xfs_rtrefcount_btree.c                 |   10 
 fs/xfs/libxfs/xfs_rtrmap_btree.c                     |   27 -
 fs/xfs/libxfs/xfs_rtrmap_btree.h                     |    5 
 fs/xfs/scrub/rcbag.c                                 |   47 --
 fs/xfs/scrub/rcbag_btree.c                           |   15 
 fs/xfs/scrub/rcbag_btree.h                           |    5 
 fs/xfs/scrub/rmap_repair.c                           |   55 ---
 fs/xfs/scrub/rtrmap_repair.c                         |   49 ---
 fs/xfs/scrub/trace.h                                 |   13 
 fs/xfs/scrub/xfbtree.c                               |  306 ++-----------------
 fs/xfs/scrub/xfbtree.h                               |   34 --
 19 files changed, 154 insertions(+), 583 deletions(-)

             reply	other threads:[~2024-01-03 20:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 20:38 Christoph Hellwig [this message]
2024-01-03 20:38 ` [PATCH 1/5] xfs: remove the in-memory btree header block Christoph Hellwig
2024-01-04  1:24   ` Darrick J. Wong
2024-01-04  6:27     ` Christoph Hellwig
2024-01-04 17:25       ` Darrick J. Wong
2024-01-03 20:38 ` [PATCH 2/5] xfs: remove struct xfboff_bitmap Christoph Hellwig
2024-01-03 20:38 ` [PATCH 3/5] xfs: remove bc_ino.flags Christoph Hellwig
2024-01-04  1:10   ` Darrick J. Wong
2024-01-03 20:38 ` [PATCH 4/5] xfs: factor out a xfs_btree_owner helper Christoph Hellwig
2024-01-04  1:14   ` Darrick J. Wong
2024-01-04  6:28     ` Christoph Hellwig
2024-01-03 20:38 ` [PATCH 5/5] xfs: embedd struct xfbtree into the owning structure Christoph Hellwig
2024-01-04  1:21   ` Darrick J. Wong
2024-01-04  6:32     ` Christoph Hellwig
2024-01-04  7:14       ` Darrick J. Wong
2024-01-04  7:17         ` Christoph Hellwig
2024-01-04  7:22           ` Darrick J. Wong
2024-01-04 19:28             ` Darrick J. Wong
2024-01-05  4:27               ` Christoph Hellwig

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=20240103203836.608391-1-hch@lst.de \
    --to=hch@lst.de \
    --cc=chandan.babu@oracle.com \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@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).