Commit 16b837eb authored by Stefan Roesch's avatar Stefan Roesch Committed by Andrew Morton
Browse files

mm: document /sys/class/bdi/<bdi>/strict_limit knob 

This documents the new /sys/class/bdi/<bdi>/strict_limit knob.

Link: https://lkml.kernel.org/r/20221119005215.3052436-4-shr@devkernel.io


Signed-off-by: default avatarStefan Roesch <shr@devkernel.io>
Cc: Chris Mason <clm@meta.com>
Cc: Jens Axboe <axboe@kernel.dk>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
parent 27bbe9d4

Documentation/ABI/testing/sysfs-class-bdi

+11 −0
Original line number Diff line number Diff line
@@ -55,6 +55,17 @@ Description: 
	mount that is prone to get stuck, or a FUSE mount which cannot

	be trusted to play fair.



	(read-write)

What:		/sys/class/bdi/<bdi>/strict_limit

Date:		October 2022

Contact:	Stefan Roesch <shr@devkernel.io>

Description:

	Forces per-BDI checks for the share of given device in the write-back

	cache even before the global background dirty limit is reached. This

	is useful in situations where the global limit is much higher than

	affordable for given relatively slow (or untrusted) device. Turning

	strictlimit on has no visible effect if max_ratio is equal to 100%.



	(read-write)

What:		/sys/class/bdi/<bdi>/stable_pages_required

Date:		January 2008