[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250727173959.160835-4-yizhou.tang@shopee.com>
Date: Mon, 28 Jul 2025 01:39:59 +0800
From: Tang Yizhou <yizhou.tang@...pee.com>
To: axboe@...nel.dk,
hch@....de,
jack@...e.cz
Cc: linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org,
tangyeechou@...il.com,
Tang Yizhou <yizhou.tang@...pee.com>
Subject: [PATCH v3 3/3] blk-wbt: doc: Update the doc of the wbt_lat_usec interface
From: Tang Yizhou <yizhou.tang@...pee.com>
The symbol wb_window_usec cannot be found. Update the doc to reflect the
latest implementation, in other words, the debugfs interface
'curr_win_nsec'.
Signed-off-by: Tang Yizhou <yizhou.tang@...pee.com>
---
Documentation/ABI/stable/sysfs-block | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/ABI/stable/sysfs-block b/Documentation/ABI/stable/sysfs-block
index 4ba771b56b3b..a3cf841ebdff 100644
--- a/Documentation/ABI/stable/sysfs-block
+++ b/Documentation/ABI/stable/sysfs-block
@@ -731,7 +731,7 @@ Contact: linux-block@...r.kernel.org
Description:
[RW] If the device is registered for writeback throttling, then
this file shows the target minimum read latency. If this latency
- is exceeded in a given window of time (see wb_window_usec), then
+ is exceeded in a given window of time (see curr_win_nsec), then
the writeback throttling will start scaling back writes. Writing
a value of '0' to this file disables the feature. Writing a
value of '-1' to this file resets the value to the default
--
2.25.1
Powered by blists - more mailing lists