From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: darrick.wong@oracle.com
Cc: linux-xfs@vger.kernel.org
Subject: [PATCH v2 0/5] xfs: rework online repair incore bitmap
Date: Tue, 29 Oct 2019 16:30:52 -0700 [thread overview]
Message-ID: <157239185264.1267044.16039786238721573306.stgit@magnolia> (raw)
Hi all,
In this series, we make some changes to the incore bitmap code: First,
we shorten the prefix to 'xbitmap'. Then, we rework some utility
functions for later use by online repair and clarify how the walk
functions are supposed to be used.
Finally, we use all these new pieces to convert the incore bitmap to use
an interval tree instead of linked lists. This lifts the limitation
that callers had to be careful not to set a range that was already set;
and gets us ready for the btree rebuilder functions needing to be able
to set bits in a bitmap and generate maximal contiguous extents for the
set ranges.
If you're going to start using this mess, you probably ought to just
pull from my git trees, which are linked below.
This is an extraordinary way to destroy everything. Enjoy!
Comments and questions are, as always, welcome.
--D
kernel git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfs-linux.git/log/?h=repair-bitmap-rework
next reply other threads:[~2019-10-29 23:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 23:30 Darrick J. Wong [this message]
2019-10-29 23:30 ` [PATCH 1/5] xfs: rename xfs_bitmap to xbitmap Darrick J. Wong
2019-10-29 23:31 ` [PATCH 2/5] xfs: replace open-coded bitmap weight logic Darrick J. Wong
2019-10-29 23:31 ` [PATCH 3/5] xfs: remove the for_each_xbitmap_ helpers Darrick J. Wong
2019-10-29 23:31 ` [PATCH 4/5] xfs: drop the _safe behavior from the xbitmap foreach macro Darrick J. Wong
2019-10-29 23:31 ` [PATCH 5/5] xfs: convert xbitmap to interval tree Darrick J. Wong
2020-01-01 1:01 [PATCH v2 0/5] xfs: rework online repair incore bitmap Darrick J. Wong
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=157239185264.1267044.16039786238721573306.stgit@magnolia \
--to=darrick.wong@oracle.com \
--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 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.