linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Carlos Maiolino <cem@kernel.org>, linux-xfs@vger.kernel.org
Cc: Christoph Hellwig <hch@lst.de>
Subject: [PATCH] xfs: Select XFS_RT if BLK_DEV_ZONED is enabled
Date: Wed,  6 Aug 2025 13:34:49 +0900	[thread overview]
Message-ID: <20250806043449.728373-1-dlemoal@kernel.org> (raw)

Enabling XFS realtime subvolume (XFS_RT) is mandatory to support zoned
block devices. If CONFIG_BLK_DEV_ZONED is enabled, automatically select
CONFIG_XFS_RT to allow users to format zoned block devices using XFS.

Also improve the description of the XFS_RT configuration option to
document that it is reuired for zoned block devices.

Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
---
 fs/xfs/Kconfig | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/fs/xfs/Kconfig b/fs/xfs/Kconfig
index ae0ca6858496..c77118e96b82 100644
--- a/fs/xfs/Kconfig
+++ b/fs/xfs/Kconfig
@@ -5,6 +5,7 @@ config XFS_FS
 	select EXPORTFS
 	select CRC32
 	select FS_IOMAP
+	select XFS_RT if BLK_DEV_ZONED
 	help
 	  XFS is a high performance journaling filesystem which originated
 	  on the SGI IRIX platform.  It is completely multi-threaded, can
@@ -116,6 +117,15 @@ config XFS_RT
 	  from all other requests, and this can be done quite transparently
 	  to applications via the inherit-realtime directory inode flag.
 
+	  This option is mandatory to support zoned block devices. For these
+	  devices, the realtime subvolume must be backed by a zoned block
+	  device and a regular block device used as the main device (for
+	  metadata). If the zoned block device is a host-managed SMR hard-disk
+	  containing conventional zones at the beginning of its address space,
+	  XFS will use the disk conventional zones as the main device and the
+	  remaining sequential write required zones as the backing storage for
+	  the realtime subvolume.
+
 	  See the xfs man page in section 5 for additional information.
 
 	  If unsure, say N.
-- 
2.50.1


             reply	other threads:[~2025-08-06  4:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <04bqii558CCUiFEGBhKdf6qd18qly22OSKw2E3RSDAyvVmxUF09ljpQZ7lIfwSBhPXEsfzj1XUcZ29zXkR2jyQ==@protonmail.internalid>
2025-08-06  4:34 ` Damien Le Moal [this message]
2025-08-06  7:46   ` [PATCH] xfs: Select XFS_RT if BLK_DEV_ZONED is enabled Carlos Maiolino
2025-08-06  8:04     ` Damien Le Moal
2025-08-06  8:45       ` Carlos Maiolino
2025-08-06  9:35         ` Damien Le Moal
2025-08-07  7:33           ` Carlos Maiolino
2025-08-07  7:40             ` Damien Le Moal
2025-08-11 10:50     ` Christoph Hellwig
2025-08-11 10:56       ` Carlos Maiolino
2025-08-12  2:41         ` Damien Le Moal

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=20250806043449.728373-1-dlemoal@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=cem@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).