All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tao Cui <cui.tao@linux.dev>
To: Tejun Heo <tj@kernel.org>
Cc: cui.tao@linux.dev, josef@toxicopanda.com, axboe@kernel.dk,
	cgroups@vger.kernel.org, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
	andrii@kernel.org, eddyz87@gmail.com, ast@kernel.org,
	daniel@iogearbox.net, linux-kselftest@vger.kernel.org,
	Tao Cui <cuitao@kylinos.cn>,
	ameryhung@gmail.com, alexei.starovoitov@gmail.com
Subject: Re: [RFC PATCH v10 3/4] blk-iocost: add iocost_ioc_tick tracepoint for per-period device summary
Date: Mon, 19 Oct 2026 17:44:10 +0800	[thread overview]
Message-ID: <8f67b745-d63f-4d3f-9672-7bad7ce0e436@linux.dev> (raw)
In-Reply-To: <b76b821edba101b68f085f03e8613d7c@kernel.org>

Hello Tejun,

在 2026/10/17 01:49, Tejun Heo 写道:
> Hello, Tao.
> 
> On Sat, 03 Oct 2026 20:40:44 +0800, Tao Cui wrote:
>> + * Periodic per-device summary, emitted once per period from the tail of
>> + * ioc_timer_fn().  Unlike the state-change events above, this fires every
> 
> The event is emitted before the vrate adjustment and the period
> transition, not from the tail.
> 
Updated both the commit message and the comment to say that the event
is emitted before the vrate adjustment and the period transition.

>> +		/* whether the controller still has active iocgs */
>> +		__field(int, running)
> 
> nr_active counts every entry on ioc->active_iocgs, and ioc->lock is held
> from the count to the emit point, so running always equals active != 0.
> Maybe drop the field?
> 
Dropped, along with the printk column and the corresponding commit
message paragraph. With the lock held across the count and the
tracepoint emission, it always equals active != 0, so it carries no
additional information.

Thanks,
Tao

> Thanks.
> 


  reply	other threads:[~2026-10-19  9:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03 12:40 [RFC PATCH v10 0/4] blk-iocost: add BPF struct_ops cost model support Tao Cui
2026-10-03 12:40 ` [RFC PATCH v10 1/4] " Tao Cui
2026-10-03 13:21   ` bot+bpf-ci
2026-10-03 17:56   ` sashiko-bot
2026-10-03 20:45   ` Alexei Starovoitov
2026-10-16 17:49   ` Tejun Heo
2026-10-19  9:27     ` Tao Cui
2026-10-03 12:40 ` [RFC PATCH v10 2/4] selftests/bpf: add iocost cost model test Tao Cui
2026-10-16 17:49   ` Tejun Heo
2026-10-19  9:38     ` Tao Cui
2026-10-03 12:40 ` [RFC PATCH v10 3/4] blk-iocost: add iocost_ioc_tick tracepoint for per-period device summary Tao Cui
2026-10-16 17:49   ` Tejun Heo
2026-10-19  9:44     ` Tao Cui [this message]
2026-10-03 12:40 ` [RFC PATCH v10 4/4] docs: cgroup-v2: document the iocost BPF cost model attachment Tao Cui
2026-10-16 17:49   ` Tejun Heo
2026-10-19  9:50     ` Tao Cui
2026-10-15 12:00 ` [RFC PATCH v10 0/4] blk-iocost: add BPF struct_ops cost model support Tao Cui
2026-10-16 17:49   ` Tejun Heo
2026-10-19  8:47     ` Tao Cui

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8f67b745-d63f-4d3f-9672-7bad7ce0e436@linux.dev \
    --to=cui.tao@linux.dev \
    --cc=alexei.starovoitov@gmail.com \
    --cc=ameryhung@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=bpf@vger.kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=cuitao@kylinos.cn \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=josef@toxicopanda.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.