summaryrefslogtreecommitdiff
path: root/Documentation/admin-guide
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2025-05-01 15:11:17 -0700
committerJakub Kicinski <kuba@kernel.org>2025-05-01 15:11:38 -0700
commit337079d31fb160959f87d7aa22a85b123c500c48 (patch)
treef32b3019ffb563257c1fc43159229adcb54cc549 /Documentation/admin-guide
parentdeeed351e982ac4d521598375b34b071304533b0 (diff)
parentebd297a2affadb6f6f4d2e5d975c1eda18ac762d (diff)
Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
Cross-merge networking fixes after downstream PR (net-6.15-rc5). No conflicts or adjacent changes. Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'Documentation/admin-guide')
-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.