From: Chandan Babu R <chandan.babu@oracle.com>
To: linux-xfs@vger.kernel.org
Cc: Chandan Babu R <chandan.babu@oracle.com>,
djwong@kernel.org, david@fromorbit.com
Subject: [PATCH V5 06/20] xfsprogs: Use basic types to define xfs_log_dinode's di_nextents and di_anextents
Date: Fri, 21 Jan 2022 10:50:05 +0530 [thread overview]
Message-ID: <20220121052019.224605-7-chandan.babu@oracle.com> (raw)
In-Reply-To: <20220121052019.224605-1-chandan.babu@oracle.com>
A future commit will increase the width of xfs_extnum_t in order to facilitate
larger per-inode extent counters. Hence this patch now uses basic types to
define xfs_log_dinode->[di_nextents|dianextents].
Signed-off-by: Chandan Babu R <chandan.babu@oracle.com>
---
libxfs/xfs_log_format.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libxfs/xfs_log_format.h b/libxfs/xfs_log_format.h
index b322db52..fd66e702 100644
--- a/libxfs/xfs_log_format.h
+++ b/libxfs/xfs_log_format.h
@@ -396,8 +396,8 @@ struct xfs_log_dinode {
xfs_fsize_t di_size; /* number of bytes in file */
xfs_rfsblock_t di_nblocks; /* # of direct & btree blocks used */
xfs_extlen_t di_extsize; /* basic/minimum extent size for file */
- xfs_extnum_t di_nextents; /* number of extents in data fork */
- xfs_aextnum_t di_anextents; /* number of extents in attribute fork*/
+ uint32_t di_nextents; /* number of extents in data fork */
+ uint16_t di_anextents; /* number of extents in attribute fork*/
uint8_t di_forkoff; /* attr fork offs, <<3 for 64b align */
int8_t di_aformat; /* format of attr fork's data */
uint32_t di_dmevmask; /* DMIG event mask */
--
2.30.2
next prev parent reply other threads:[~2022-01-21 5:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 5:19 [PATCH V5 00/20] xfsprogs: Extend per-inode extent counters Chandan Babu R
2022-01-21 5:20 ` [PATCH V5 01/20] xfs_repair: check filesystem geometry before allowing upgrades Chandan Babu R
2022-01-21 5:20 ` [PATCH V5 02/20] xfsprogs: Move extent count limits to xfs_format.h Chandan Babu R
2022-01-21 5:20 ` [PATCH V5 03/20] xfsprogs: Introduce xfs_iext_max_nextents() helper Chandan Babu R
2022-01-21 5:20 ` [PATCH V5 04/20] xfsprogs: Use xfs_extnum_t instead of basic data types Chandan Babu R
2022-01-21 5:20 ` [PATCH V5 05/20] xfsprogs: Introduce xfs_dfork_nextents() helper Chandan Babu R
2022-01-21 5:20 ` Chandan Babu R [this message]
2022-01-21 5:20 ` [PATCH V5 07/20] xfsprogs: Promote xfs_extnum_t and xfs_aextnum_t to 64 and 32-bits respectively Chandan Babu R
2022-01-21 5:20 ` [PATCH V5 08/20] xfsprogs: Introduce XFS_SB_FEAT_INCOMPAT_NREXT64 and associated per-fs feature bit Chandan Babu R
2022-01-21 5:20 ` [PATCH V5 09/20] xfsprogs: Introduce XFS_FSOP_GEOM_FLAGS_NREXT64 Chandan Babu R
2022-01-21 5:20 ` [PATCH V5 10/20] xfsprogs: Introduce XFS_DIFLAG2_NREXT64 and associated helpers Chandan Babu R
2022-01-21 5:20 ` [PATCH V5 11/20] xfsprogs: Use xfs_rfsblock_t to count maximum blocks that can be used by BMBT Chandan Babu R
2022-01-21 5:20 ` [PATCH V5 12/20] xfsprogs: Introduce macros to represent new maximum extent counts for data/attr forks Chandan Babu R
2022-01-21 5:20 ` [PATCH V5 13/20] xfsprogs: Introduce per-inode 64-bit extent counters Chandan Babu R
2022-01-21 5:20 ` [PATCH V5 14/20] xfsprogs: Conditionally upgrade existing inodes to use " Chandan Babu R
2022-01-21 5:20 ` [PATCH V5 15/20] xfsprogs: Enable bulkstat ioctl to support " Chandan Babu R
2022-02-01 19:29 ` Darrick J. Wong
2022-01-21 5:20 ` [PATCH V5 16/20] xfsprogs: Add XFS_SB_FEAT_INCOMPAT_NREXT64 to the list of supported flags Chandan Babu R
2022-01-21 5:20 ` [PATCH V5 17/20] xfsprogs: xfs_info: Report NREXT64 feature status Chandan Babu R
2022-01-21 5:20 ` [PATCH V5 18/20] xfsprogs: Add mkfs option to create filesystem with large extent counters Chandan Babu R
2022-01-25 0:33 ` Darrick J. Wong
2022-01-21 5:20 ` [PATCH V5 19/20] xfsprogs: Add support for upgrading to NREXT64 feature Chandan Babu R
2022-01-25 0:35 ` Darrick J. Wong
2022-01-21 5:20 ` [PATCH V5 20/20] xfsprogs: Define max extent length based on on-disk format definition Chandan Babu R
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=20220121052019.224605-7-chandan.babu@oracle.com \
--to=chandan.babu@oracle.com \
--cc=david@fromorbit.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