From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: darrick.wong@oracle.com
Cc: linux-xfs@vger.kernel.org
Subject: [PATCH 1/2] design: document the new inode btree counter feature
Date: Tue, 27 Oct 2020 18:10:18 -0700 [thread overview]
Message-ID: <160384741848.1365004.5354796889293226533.stgit@magnolia> (raw)
In-Reply-To: <160384741244.1365004.6341029408891306870.stgit@magnolia>
From: Darrick J. Wong <darrick.wong@oracle.com>
Update the ondisk format documentation to discuss the inode btree
counter feature.
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
---
.../allocation_groups.asciidoc | 21 ++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/design/XFS_Filesystem_Structure/allocation_groups.asciidoc b/design/XFS_Filesystem_Structure/allocation_groups.asciidoc
index 992615d..2e78f56 100644
--- a/design/XFS_Filesystem_Structure/allocation_groups.asciidoc
+++ b/design/XFS_Filesystem_Structure/allocation_groups.asciidoc
@@ -405,6 +405,13 @@ reference counts of AG blocks. This enables files to share data blocks safely.
See the section about xref:Reflink_Deduplication[reflink and deduplication] for
more details.
+| +XFS_SB_FEAT_RO_COMPAT_INOBTCNT+ |
+Inode B+tree block counters. Each allocation group's inode (AGI) header
+tracks the number of blocks in each of the inode B+trees. This allows us
+to have a slightly higher level of redundancy over the shape of the inode
+btrees, and decreases the amount of time to compute the metadata B+tree
+preallocations at mount time.
+
|=====
*sb_features_incompat*::
@@ -928,6 +935,10 @@ struct xfs_agi {
__be32 agi_free_root;
__be32 agi_free_level;
+
+ __be32 agi_iblocks;
+ __be32 agi_fblocks;
+
}
----
*agi_magicnum*::
@@ -984,6 +995,16 @@ B+tree.
*agi_free_level*::
Specifies the number of levels in the free inode B+tree.
+*agi_iblocks*::
+The number of blocks in the inode B+tree, including the root.
+This field is zero if the +XFS_SB_FEAT_RO_COMPAT_INOBTCNT+ feature is not
+enabled.
+
+*agi_fblocks*::
+The number of blocks in the free inode B+tree, including the root.
+This field is zero if the +XFS_SB_FEAT_RO_COMPAT_INOBTCNT+ feature is not
+enabled.
+
[[Inode_Btrees]]
== Inode B+trees
next prev parent reply other threads:[~2020-10-29 1:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 1:10 [PATCH 0/2] xfs-documentation: format updates for 5.10 Darrick J. Wong
2020-10-28 1:10 ` Darrick J. Wong [this message]
2020-10-28 1:10 ` [PATCH 2/2] design: document changes for the bigtime feature Darrick J. Wong
2021-03-26 2:48 [PATCHSET 0/2] xfs-documentation: format updates for 5.10 Darrick J. Wong
2021-03-26 2:48 ` [PATCH 1/2] design: document the new inode btree counter feature Darrick J. Wong
2021-04-02 6:46 ` 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=160384741848.1365004.5354796889293226533.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 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).