All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: linux-xfs@vger.kernel.org, Carlos Maiolino <cem@kernel.org>
Subject: [PATCH] xfs: Improve CONFIG_XFS_RT Kconfig help
Date: Mon, 13 Oct 2025 12:08:29 +0900	[thread overview]
Message-ID: <20251013030829.672060-1-dlemoal@kernel.org> (raw)

Improve the description of the XFS_RT configuration option to document
that this option is required for zoned block devices.

Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
---
 fs/xfs/Kconfig | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/fs/xfs/Kconfig b/fs/xfs/Kconfig
index 8930d5254e1d..d66d517c99a9 100644
--- a/fs/xfs/Kconfig
+++ b/fs/xfs/Kconfig
@@ -119,6 +119,15 @@ config XFS_RT
 
 	  See the xfs man page in section 5 for additional information.
 
+	  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.
+
 	  If unsure, say N.
 
 config XFS_DRAIN_INTENTS
-- 
2.51.0


             reply	other threads:[~2025-10-13  3:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13  3:08 Damien Le Moal [this message]
2025-10-21  9:37 ` [PATCH] xfs: Improve CONFIG_XFS_RT Kconfig help Carlos Maiolino
     [not found] <kKXUIiXOoMsPMpRsmYCR1_l18oSyQGIV5yApvbbZS23U9u_Tz1D3npu22B_aOWZplsFFJ_Bl_UmoTmTLGm90Fg==@protonmail.internalid>
2025-08-07  5:56 ` Damien Le Moal
2025-08-11 10:44   ` Christoph Hellwig
2025-08-11 12:07   ` Carlos Maiolino

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=20251013030829.672060-1-dlemoal@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=cem@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 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.