summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHans Holmberg <Hans.Holmberg@wdc.com>2025-04-22 11:50:07 +0000
committerCarlos Maiolino <cem@kernel.org>2025-04-22 16:05:24 +0200
commitf0447f80aec83f1699d599c94618bb5c323963e6 (patch)
treeacbcc3ae62d9afce53740c6016357896c75449db
parentbd7c19331913b955a7823e6315ca16bbcc65aeff (diff)
xfs: remove duplicate Zoned Filesystems sections in admin-guide
Remove the duplicated section and while at it, turn spaces into tabs. Signed-off-by: Hans Holmberg <hans.holmberg@wdc.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com> Fixes: c7b67ddc3c99 ("xfs: document zoned rt specifics in admin-guide") Signed-off-by: Carlos Maiolino <cem@kernel.org>
-rw-r--r--Documentation/admin-guide/xfs.rst29
1 files changed, 8 insertions, 21 deletions
diff --git a/Documentation/admin-guide/xfs.rst b/Documentation/admin-guide/xfs.rst
index 3e76276bd488..5becb441c3cb 100644
--- a/Documentation/admin-guide/xfs.rst
+++ b/Documentation/admin-guide/xfs.rst
@@ -562,7 +562,7 @@ The interesting knobs for XFS workqueues are as follows:
Zoned Filesystems
=================
-For zoned file systems, the following attribute is exposed in:
+For zoned file systems, the following attributes are exposed in:
/sys/fs/xfs/<dev>/zoned/
@@ -572,23 +572,10 @@ For zoned file systems, the following attribute is exposed in:
is limited by the capabilities of the backing zoned device, file system
size and the max_open_zones mount option.
-Zoned Filesystems
-=================
-
-For zoned file systems, the following attributes are exposed in:
-
- /sys/fs/xfs/<dev>/zoned/
-
- max_open_zones (Min: 1 Default: Varies Max: UINTMAX)
- This read-only attribute exposes the maximum number of open zones
- available for data placement. The value is determined at mount time and
- is limited by the capabilities of the backing zoned device, file system
- size and the max_open_zones mount option.
-
- zonegc_low_space (Min: 0 Default: 0 Max: 100)
- Define a percentage for how much of the unused space that GC should keep
- available for writing. A high value will reclaim more of the space
- occupied by unused blocks, creating a larger buffer against write
- bursts at the cost of increased write amplification. Regardless
- of this value, garbage collection will always aim to free a minimum
- amount of blocks to keep max_open_zones open for data placement purposes.
+ zonegc_low_space (Min: 0 Default: 0 Max: 100)
+ Define a percentage for how much of the unused space that GC should keep
+ available for writing. A high value will reclaim more of the space
+ occupied by unused blocks, creating a larger buffer against write
+ bursts at the cost of increased write amplification. Regardless
+ of this value, garbage collection will always aim to free a minimum
+ amount of blocks to keep max_open_zones open for data placement purposes.