On Mon 28-07-25 01:39:59, Tang Yizhou wrote: > From: Tang Yizhou <yizhou.tang@xxxxxxxxxx> > > 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@xxxxxxxxxx> Looks good! Feel free to add: Reviewed-by: Jan Kara <jack@xxxxxxx> Honza > --- > 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@xxxxxxxxxxxxxxx > 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 > -- Jan Kara <jack@xxxxxxxx> SUSE Labs, CR
