[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <939f45b2-4481-422a-a747-012808953d7f@kernel.org>
Date: Mon, 28 Jul 2025 01:09:07 +0800
From: Yu Kuai <yukuai@...nel.org>
To: Tang Yizhou <yizhou.tang@...pee.com>, axboe@...nel.dk, hch@....de,
jack@...e.cz
Cc: linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
tangyeechou@...il.com
Subject: Re: [PATCH v2 3/3] blk-wbt: doc: Update the doc of the wbt_lat_usec
interface
Hi,
在 2025/7/28 0:47, Tang Yizhou 写道:
> 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 cur_win_nsec member of struct
> rq_wb.
>
> 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..277d89815edd 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 cur_win_nsec), then
Is this a typo? Jan suggested curr_win_nsec from v1.
BTW, I don't mind rename rwb->cur_win_nsec to curr_win_nsec as well.
Thanks,
Kuai
> 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
Powered by blists - more mailing lists