aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStefan Roesch <[email protected]>2022-11-18 16:52:04 -0800
committerAndrew Morton <[email protected]>2022-11-30 15:59:04 -0800
commitc354d9268d7825eb8643f658c5091079d4f11a4a (patch)
tree02e3395547a1d229c4ba314e2d747d203bab994a
parentc56e049a5e401a177c7c9b39a3bcc973ff5cec0b (diff)
mm: document /sys/class/bdi/<bdi>/max_bytes knob
This documents the new /sys/class/bdi/<bdi>/max_bytes knob. Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Stefan Roesch <[email protected]> Cc: Chris Mason <[email protected]> Cc: Jens Axboe <[email protected]> Signed-off-by: Andrew Morton <[email protected]>
-rw-r--r--Documentation/ABI/testing/sysfs-class-bdi14
1 files changed, 14 insertions, 0 deletions
diff --git a/Documentation/ABI/testing/sysfs-class-bdi b/Documentation/ABI/testing/sysfs-class-bdi
index 68b5d4018c2f..580f723de049 100644
--- a/Documentation/ABI/testing/sysfs-class-bdi
+++ b/Documentation/ABI/testing/sysfs-class-bdi
@@ -56,6 +56,20 @@ Description:
be trusted to play fair.
(read-write)
+
+What: /sys/class/bdi/<bdi>/max_bytes
+Date: October 2022
+Contact: Stefan Roesch <[email protected]>
+Description:
+ Allows limiting a particular device to use not more than the
+ given 'max_bytes' of the write-back cache. This is useful in
+ situations where we want to avoid one device taking all or
+ most of the write-back cache. For example in case of an NFS
+ mount that is prone to get stuck, a FUSE mount which cannot be
+ trusted to play fair, or a nbd device.
+
+ (read-write)
+
What: /sys/class/bdi/<bdi>/strict_limit
Date: October 2022
Contact: Stefan Roesch <[email protected]>