Re: [RFC PATCH v13 2/4] blk-iocost: add iocost_ioc_tick tracepoint for per-period device summary

From: Tejun Heo

Date: Mon Nov 16 2026 - 12:30:29 EST


On Fri, Nov 06, 2026 at 08:23:54PM +0800, Tao Cui wrote:
> Add iocost_ioc_tick, emitted once per period from ioc_timer_fn() with
> the overall controller state: period_us, vrate, busy_level, active iocg
> count and usage percentage. busy_level, cur_period, nr_active and
> usage_us_sum are complete at the emission point. usage is wall time
> over wall time, summed over iocgs, and is not capped at 100. vrate and
> period_us reflect the current controller state, which an io.cost.qos
> write may have changed mid-period.
>
> The event fires every period the controller is running, including
> steady states, plus one final tick before the controller goes idle, so
> the transition to dormancy is directly visible. The active iocg count
> is only gathered when the tracepoint is enabled.
>
> Suggested-by: Tejun Heo <tj@xxxxxxxxxx>
> Signed-off-by: Tao Cui <cuitao@xxxxxxxxxx>

Acked-by: Tejun Heo <tj@xxxxxxxxxx>

Thanks.

--
tejun