From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Carlos Maiolino <cem@kernel.org>,
Hans Holmberg <hans.holmberg@wdc.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 33/43] xfs: enable fsmap reporting for internal RT devices
Date: Thu, 6 Feb 2025 20:39:01 -0800 [thread overview]
Message-ID: <20250207043901.GP21808@frogsfrogsfrogs> (raw)
In-Reply-To: <20250206064511.2323878-34-hch@lst.de>
On Thu, Feb 06, 2025 at 07:44:49AM +0100, Christoph Hellwig wrote:
> File system with internal RT devices are a bit odd in that we need
> to report AGs and RGs. To make this happen use separate synthetic
> fmr_device values for the different sections instead of the dev_t
> mapping used by other XFS configurations.
>
> The data device is reported as file system metadata before the
> start of the RGs for the synthetic RT fmr_device.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
I've thought a bit more about something you said last time:
> The bmbt values are all relative to rtstart, the daddr translation is
> what adds the offset. So if we want to take the offset out of the
> fsmap reporting, I'll need new helpers to not add it or manually
> subtract it afterwards. If that's preferred it should be doable, even
> if the fsmap code keeps confusing me more each time I look at it.
The fmr_physical addresses of the fsmaps reported for the "XFS_DEV_RT"
device (aka when sb_rtstart > 0) are relative to the start of the data
device, right? In a way, that makes it easier to figure out how to set
up a media scan or a block device to file translation, because the
fmr_physical number you feed in and get out of fsmap always matches the
device LBA.
So assuming that's still the case, then I like this enough to say
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> fs/xfs/libxfs/xfs_fs.h | 9 +++++
> fs/xfs/xfs_fsmap.c | 80 +++++++++++++++++++++++++++++++++---------
> 2 files changed, 72 insertions(+), 17 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_fs.h b/fs/xfs/libxfs/xfs_fs.h
> index 5e66fb2b2cc7..12463ba766da 100644
> --- a/fs/xfs/libxfs/xfs_fs.h
> +++ b/fs/xfs/libxfs/xfs_fs.h
> @@ -1082,6 +1082,15 @@ struct xfs_rtgroup_geometry {
> #define XFS_IOC_COMMIT_RANGE _IOW ('X', 131, struct xfs_commit_range)
> /* XFS_IOC_GETFSUUID ---------- deprecated 140 */
>
> +/*
> + * Devices supported by a single XFS file system. Reported in fsmaps fmr_device
> + * when using internal RT devices.
> + */
> +enum xfs_device {
> + XFS_DEV_DATA = 1,
> + XFS_DEV_LOG = 2,
> + XFS_DEV_RT = 3,
> +};
>
> #ifndef HAVE_BBMACROS
> /*
> diff --git a/fs/xfs/xfs_fsmap.c b/fs/xfs/xfs_fsmap.c
> index 917d4d0e51b3..a4bc1642fe56 100644
> --- a/fs/xfs/xfs_fsmap.c
> +++ b/fs/xfs/xfs_fsmap.c
> @@ -879,17 +879,39 @@ xfs_getfsmap_rtdev_rmapbt(
> struct xfs_mount *mp = tp->t_mountp;
> struct xfs_rtgroup *rtg = NULL;
> struct xfs_btree_cur *bt_cur = NULL;
> + xfs_daddr_t rtstart_daddr;
> xfs_rtblock_t start_rtb;
> xfs_rtblock_t end_rtb;
> xfs_rgnumber_t start_rg, end_rg;
> uint64_t eofs;
> int error = 0;
>
> - eofs = XFS_FSB_TO_BB(mp, mp->m_sb.sb_rblocks);
> + eofs = XFS_FSB_TO_BB(mp, mp->m_sb.sb_rtstart + mp->m_sb.sb_rblocks);
> if (keys[0].fmr_physical >= eofs)
> return 0;
> - start_rtb = xfs_daddr_to_rtb(mp, keys[0].fmr_physical);
> - end_rtb = xfs_daddr_to_rtb(mp, min(eofs - 1, keys[1].fmr_physical));
> +
> + rtstart_daddr = XFS_FSB_TO_BB(mp, mp->m_sb.sb_rtstart);
> + if (keys[0].fmr_physical < rtstart_daddr) {
> + struct xfs_fsmap_irec frec = {
> + .owner = XFS_RMAP_OWN_FS,
> + .len_daddr = rtstart_daddr,
> + };
> +
> + /* Adjust the low key if we are continuing from where we left off. */
> + if (keys[0].fmr_length > 0) {
> + info->low_daddr = keys[0].fmr_physical + keys[0].fmr_length;
> + return 0;
> + }
> +
> + /* Fabricate an rmap entry for space occupied by the data dev */
> + error = xfs_getfsmap_helper(tp, info, &frec);
> + if (error)
> + return error;
> + }
> +
> + start_rtb = xfs_daddr_to_rtb(mp, rtstart_daddr + keys[0].fmr_physical);
> + end_rtb = xfs_daddr_to_rtb(mp, rtstart_daddr +
> + min(eofs - 1, keys[1].fmr_physical));
>
> info->missing_owner = XFS_FMR_OWN_FREE;
>
> @@ -1004,22 +1026,40 @@ xfs_getfsmap_rtdev_rmapbt(
> }
> #endif /* CONFIG_XFS_RT */
>
> +static uint32_t
> +xfs_getfsmap_device(
> + struct xfs_mount *mp,
> + enum xfs_device dev)
> +{
> + if (mp->m_sb.sb_rtstart)
> + return dev;
> +
> + switch (dev) {
> + case XFS_DEV_DATA:
> + return new_encode_dev(mp->m_ddev_targp->bt_dev);
> + case XFS_DEV_LOG:
> + return new_encode_dev(mp->m_logdev_targp->bt_dev);
> + case XFS_DEV_RT:
> + if (!mp->m_rtdev_targp)
> + break;
> + return new_encode_dev(mp->m_rtdev_targp->bt_dev);
> + }
> +
> + return -1;
> +}
> +
> /* Do we recognize the device? */
> STATIC bool
> xfs_getfsmap_is_valid_device(
> struct xfs_mount *mp,
> struct xfs_fsmap *fm)
> {
> - if (fm->fmr_device == 0 || fm->fmr_device == UINT_MAX ||
> - fm->fmr_device == new_encode_dev(mp->m_ddev_targp->bt_dev))
> - return true;
> - if (mp->m_logdev_targp &&
> - fm->fmr_device == new_encode_dev(mp->m_logdev_targp->bt_dev))
> - return true;
> - if (mp->m_rtdev_targp &&
> - fm->fmr_device == new_encode_dev(mp->m_rtdev_targp->bt_dev))
> - return true;
> - return false;
> + return fm->fmr_device == 0 ||
> + fm->fmr_device == UINT_MAX ||
> + fm->fmr_device == xfs_getfsmap_device(mp, XFS_DEV_DATA) ||
> + fm->fmr_device == xfs_getfsmap_device(mp, XFS_DEV_LOG) ||
> + (mp->m_rtdev_targp &&
> + fm->fmr_device == xfs_getfsmap_device(mp, XFS_DEV_RT));
> }
>
> /* Ensure that the low key is less than the high key. */
> @@ -1126,7 +1166,7 @@ xfs_getfsmap(
> /* Set up our device handlers. */
> memset(handlers, 0, sizeof(handlers));
> handlers[0].nr_sectors = XFS_FSB_TO_BB(mp, mp->m_sb.sb_dblocks);
> - handlers[0].dev = new_encode_dev(mp->m_ddev_targp->bt_dev);
> + handlers[0].dev = xfs_getfsmap_device(mp, XFS_DEV_DATA);
> if (use_rmap)
> handlers[0].fn = xfs_getfsmap_datadev_rmapbt;
> else
> @@ -1134,7 +1174,7 @@ xfs_getfsmap(
> if (mp->m_logdev_targp != mp->m_ddev_targp) {
> handlers[1].nr_sectors = XFS_FSB_TO_BB(mp,
> mp->m_sb.sb_logblocks);
> - handlers[1].dev = new_encode_dev(mp->m_logdev_targp->bt_dev);
> + handlers[1].dev = xfs_getfsmap_device(mp, XFS_DEV_LOG);
> handlers[1].fn = xfs_getfsmap_logdev;
> }
> #ifdef CONFIG_XFS_RT
> @@ -1144,7 +1184,7 @@ xfs_getfsmap(
> */
> if (mp->m_rtdev_targp && (use_rmap || !xfs_has_zoned(mp))) {
> handlers[2].nr_sectors = XFS_FSB_TO_BB(mp, mp->m_sb.sb_rblocks);
> - handlers[2].dev = new_encode_dev(mp->m_rtdev_targp->bt_dev);
> + handlers[2].dev = xfs_getfsmap_device(mp, XFS_DEV_RT);
> if (use_rmap)
> handlers[2].fn = xfs_getfsmap_rtdev_rmapbt;
> else
> @@ -1234,7 +1274,13 @@ xfs_getfsmap(
>
> if (tp)
> xfs_trans_cancel(tp);
> - head->fmh_oflags = FMH_OF_DEV_T;
> +
> + /*
> + * For internal RT device we need to report different synthetic devices
> + * for a single physical device, and thus can't report the actual dev_t.
> + */
> + if (!mp->m_sb.sb_rtstart)
> + head->fmh_oflags = FMH_OF_DEV_T;
> return error;
> }
>
> --
> 2.45.2
>
>
next prev parent reply other threads:[~2025-02-07 4:39 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 6:44 support for zoned devices RFCv2 Christoph Hellwig
2025-02-06 6:44 ` [PATCH 01/43] xfs: factor out a xfs_rt_check_size helper Christoph Hellwig
2025-02-06 6:44 ` [PATCH 02/43] xfs: add a rtg_blocks helper Christoph Hellwig
2025-02-06 6:44 ` [PATCH 03/43] xfs: move xfs_bmapi_reserve_delalloc to xfs_iomap.c Christoph Hellwig
2025-02-06 6:44 ` [PATCH 04/43] xfs: skip always_cow inodes in xfs_reflink_trim_around_shared Christoph Hellwig
2025-02-06 20:13 ` Darrick J. Wong
2025-02-07 4:15 ` Christoph Hellwig
2025-02-07 4:22 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 05/43] xfs: refine the unaligned check for always COW inodes in xfs_file_dio_write Christoph Hellwig
2025-02-06 6:44 ` [PATCH 06/43] xfs: generalize the freespace and reserved blocks handling Christoph Hellwig
2025-02-06 21:29 ` Darrick J. Wong
2025-02-07 4:21 ` Christoph Hellwig
2025-02-07 4:28 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 07/43] xfs: preserve RT reservations across remounts Christoph Hellwig
2025-02-06 20:14 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 08/43] xfs: reflow xfs_dec_freecounter Christoph Hellwig
2025-02-06 20:14 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 09/43] xfs: trace in-memory freecounters Christoph Hellwig
2025-02-06 20:15 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 10/43] xfs: make metabtree reservations global Christoph Hellwig
2025-02-06 20:50 ` Darrick J. Wong
2025-02-07 4:18 ` Christoph Hellwig
2025-02-07 4:24 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 11/43] xfs: reduce metafile reservations Christoph Hellwig
2025-02-06 20:52 ` Darrick J. Wong
2025-02-07 4:19 ` Christoph Hellwig
2025-02-07 4:26 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 12/43] xfs: support XFS_BMAPI_REMAP in xfs_bmap_del_extent_delay Christoph Hellwig
2025-02-06 20:54 ` Darrick J. Wong
2025-02-07 4:19 ` Christoph Hellwig
2025-02-06 6:44 ` [PATCH 13/43] xfs: add a xfs_rtrmap_highest_rgbno helper Christoph Hellwig
2025-02-06 20:55 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 14/43] xfs: define the zoned on-disk format Christoph Hellwig
2025-02-06 21:00 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 15/43] xfs: allow internal RT devices for zoned mode Christoph Hellwig
2025-02-06 6:44 ` [PATCH 16/43] xfs: export zoned geometry via XFS_FSOP_GEOM Christoph Hellwig
2025-02-06 21:03 ` Darrick J. Wong
2025-02-07 4:20 ` Christoph Hellwig
2025-02-06 6:44 ` [PATCH 17/43] xfs: disable sb_frextents for zoned file systems Christoph Hellwig
2025-02-06 6:44 ` [PATCH 18/43] xfs: disable FITRIM for zoned RT devices Christoph Hellwig
2025-02-06 6:44 ` [PATCH 19/43] xfs: don't call xfs_can_free_eofblocks from ->release for zoned inodes Christoph Hellwig
2025-02-06 6:44 ` [PATCH 20/43] xfs: skip zoned RT inodes in xfs_inodegc_want_queue_rt_file Christoph Hellwig
2025-02-06 21:04 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 21/43] xfs: parse and validate hardware zone information Christoph Hellwig
2025-02-06 21:05 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 22/43] xfs: add the zoned space allocator Christoph Hellwig
2025-02-07 17:39 ` Darrick J. Wong
2025-02-13 5:14 ` Christoph Hellwig
2025-02-13 8:35 ` Christoph Hellwig
2025-02-17 9:20 ` Christoph Hellwig
2025-02-13 22:08 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 23/43] xfs: add support for zoned space reservations Christoph Hellwig
2025-02-07 17:52 ` Darrick J. Wong
2025-02-13 5:17 ` Christoph Hellwig
2025-02-13 22:09 ` Darrick J. Wong
2025-02-14 6:20 ` Christoph Hellwig
2025-02-14 18:25 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 24/43] xfs: implement zoned garbage collection Christoph Hellwig
2025-02-07 18:33 ` Darrick J. Wong
2025-02-13 5:22 ` Christoph Hellwig
2025-02-13 22:10 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 25/43] xfs: implement buffered writes to zoned RT devices Christoph Hellwig
2025-02-12 0:54 ` Darrick J. Wong
2025-02-13 5:39 ` Christoph Hellwig
2025-02-13 23:05 ` Darrick J. Wong
2025-02-14 6:22 ` Christoph Hellwig
2025-02-14 18:29 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 26/43] xfs: implement direct " Christoph Hellwig
2025-02-06 6:44 ` [PATCH 27/43] xfs: wire up zoned block freeing in xfs_rtextent_free_finish_item Christoph Hellwig
2025-02-06 6:44 ` [PATCH 28/43] xfs: hide reserved RT blocks from statfs Christoph Hellwig
2025-02-07 4:32 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 29/43] xfs: support growfs on zoned file systems Christoph Hellwig
2025-02-06 6:44 ` [PATCH 30/43] xfs: allow COW forks on zoned file systems in xchk_bmap Christoph Hellwig
2025-02-06 6:44 ` [PATCH 31/43] xfs: support xchk_xref_is_used_rt_space on zoned file systems Christoph Hellwig
2025-02-06 6:44 ` [PATCH 32/43] xfs: support xrep_require_rtext_inuse " Christoph Hellwig
2025-02-06 6:44 ` [PATCH 33/43] xfs: enable fsmap reporting for internal RT devices Christoph Hellwig
2025-02-07 4:39 ` Darrick J. Wong [this message]
2025-02-07 4:55 ` Christoph Hellwig
2025-02-06 6:44 ` [PATCH 34/43] xfs: disable reflink for zoned file systems Christoph Hellwig
2025-02-07 4:31 ` Darrick J. Wong
2025-02-07 4:54 ` Christoph Hellwig
2025-02-07 5:05 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 35/43] xfs: disable rt quotas " Christoph Hellwig
2025-02-07 4:31 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 36/43] xfs: enable the zoned RT device feature Christoph Hellwig
2025-02-06 6:44 ` [PATCH 37/43] xfs: support zone gaps Christoph Hellwig
2025-02-06 6:44 ` [PATCH 38/43] xfs: add a max_open_zones mount option Christoph Hellwig
2025-02-07 4:29 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 39/43] xfs: support write life time based data placement Christoph Hellwig
2025-02-12 0:27 ` Darrick J. Wong
2025-02-12 13:29 ` Hans Holmberg
2025-02-13 4:42 ` Darrick J. Wong
2025-02-13 13:03 ` Hans Holmberg
2025-02-14 6:41 ` hch
2025-02-14 12:20 ` Hans Holmberg
2025-02-14 16:21 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 40/43] xfs: wire up the show_stats super operation Christoph Hellwig
2025-02-06 6:44 ` [PATCH 41/43] xfs: export zone stats in /proc/*/mountstats Christoph Hellwig
2025-02-07 1:02 ` Darrick J. Wong
2025-02-07 4:25 ` Christoph Hellwig
2025-02-06 6:44 ` [PATCH 42/43] xfs: contain more sysfs code in xfs_sysfs.c Christoph Hellwig
2025-02-07 0:54 ` Darrick J. Wong
2025-02-06 6:44 ` [PATCH 43/43] xfs: export max_open_zones in sysfs Christoph Hellwig
2025-02-07 0:52 ` Darrick J. Wong
2025-02-07 4:23 ` Christoph Hellwig
2025-02-07 4:27 ` 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=20250207043901.GP21808@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=hans.holmberg@wdc.com \
--cc=hch@lst.de \
--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