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,
cuitao@kylinos.cn, ameryhung@gmail.com,
alexei.starovoitov@gmail.com
Subject: Re: [PATCH 3/5] selftests/bpf: add iocost cost model test
Date: Thu, 29 Oct 2026 18:30:16 +0800 [thread overview]
Message-ID: <049090ed-48f8-4360-91f2-381357a0d40f@linux.dev> (raw)
In-Reply-To: <b69d96a507aec382c279d62cfb038fa9@kernel.org>
Hello Tejun,
在 2026/10/29 04:09, Tejun Heo 写道:
> Hello, Tao.
>
> On Wed, Oct 28, 2026 at 10:35:32PM +0800, Tao Cui wrote:
>> +static bool iocost_bpf_supported(void)
>> +{
>> + FILE *f;
>> + char line[128];
>> + bool any = false, on = false;
>> ...
>> + if (strstr(line, "CONFIG_"))
>> + any = true;
>> ...
>> + return on;
>
> any is set but never read, so every test skips without /proc/config.gz.
>
I'll make the probe return whether CONFIG_BLK_CGROUP_IOCOST_BPF=y was
seen.
>> + /* isolate the configfs and cgroup mounts from the host */
>> + if (unshare(CLONE_NEWNS)) {
>
> unshare(CLONE_NEWNS) alone doesn't make the mounts private, so the
> configfs mount propagates to the host, one more per test.
>
I'll follow unshare() with mount(NULL, "/", NULL,
MS_REC | MS_PRIVATE, NULL).
>> + ASSERT_OK(configfs_write("/sys/fs/cgroup/cgroup.subtree_control",
>> + "+io"), "subtree_io");
>> + if (!ASSERT_OK(cgroup_mkdir("/sys/fs/cgroup/iocost_pairing"),
>
> The "+io" write to the root cgroup's cgroup.subtree_control is never
> reverted, the cgroups are created directly under /sys/fs/cgroup and
> test_progs stays in the root cgroup. cgroup_helpers handles all of this.
>
I'll restore the "+io" setting on exit and move the test process back
to the root cgroup before removing the test cgroups. I'll also switch
the test over to cgroup_helpers.
>> + err = iocost_model__attach(skel);
>> + if (err == -EOPNOTSUPP || err == -ENODEV) {
>> ...
>> + test__skip();
>
> -ENODEV and -EOPNOTSUPP from attaching to the test's own null_blk device
> are failures, not skips. The same goes for
> serial_test_iocost_model_streams().
>
Both become ASSERT_OK failures.
>> + ASSERT_GT(skel->bss->iocg_inits, 0, "pair_init");
>
> This passes on the root blkg alone, so it doesn't show that the test
> cgroup got iocg_init(). The same goes for eject_had_inits and
> pair_init_again.
>
Gone with the callbacks.
>> + /*
>> + * detach implicitly by closing the link fd instead of
>> + * calling bpf_link__destroy() explicitly: the release
>> + * path must detach the model just like the explicit
>> + * call does
>> + */
>> + lfd = bpf_link__fd(skel->links.iocost_2x);
>> + bpf_link__disconnect(skel->links.iocost_2x);
>> + close(lfd);
>> + skel->links.iocost_2x = NULL;
>
> This leaks libbpf's link struct. The reason in the comment doesn't hold
> either. bpf_link__destroy() on a struct_ops link does the same close().
>
I'll use bpf_link__destroy() instead.
>> +void serial_test_iocost_model_streams(void)
>> ...
>> + if (ASSERT_OK(err, "attach")) {
>> + err = readback_model(dev, model, sizeof(model));
>> + if (ASSERT_OK(err, "readback"))
>> + ASSERT_STREQ(model, "bpf", "model_bpf");
>> +
>> + bpf_link__destroy(skel->links.iocost_ms);
>
> The test never enables the controller, so iocost_ms's calc_cost() never
> runs. The multi-stream results in the cover letter aren't exercised by
> the test.
>
I'll enable the controller, move the test into a cgroup, drive IO
through the device, and assert that the model is exercised.
Thanks,
Tao
> Thanks.
>
> --
> tejun
next prev parent reply other threads:[~2026-10-29 10:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 14:35 [RFC PATCH v11 0/5] blk-iocost: BPF struct_ops cost model Tao Cui
2026-10-28 14:35 ` [PATCH 1/5] blk-iocost: move shared definitions to blk-iocost.h Tao Cui
2026-10-28 20:09 ` Tejun Heo
2026-10-29 10:04 ` Tao Cui
2026-10-28 14:35 ` [PATCH 2/5] blk-iocost: add BPF struct_ops cost model support Tao Cui
2026-10-28 15:33 ` bot+bpf-ci
2026-10-28 20:09 ` Tejun Heo
2026-10-29 10:11 ` Tao Cui
2026-10-28 14:35 ` [PATCH 3/5] selftests/bpf: add iocost cost model test Tao Cui
2026-10-28 15:33 ` bot+bpf-ci
2026-10-28 20:09 ` Tejun Heo
2026-10-29 10:30 ` Tao Cui [this message]
2026-10-28 14:35 ` [PATCH 4/5] blk-iocost: add iocost_ioc_tick tracepoint for per-period device summary Tao Cui
2026-10-28 20:09 ` Tejun Heo
2026-10-29 10:31 ` Tao Cui
2026-10-28 14:35 ` [PATCH 5/5] docs: cgroup-v2: document the iocost BPF cost model attachment Tao Cui
2026-10-28 20:09 ` Tejun Heo
2026-10-29 10:33 ` Tao Cui
2026-10-28 15:58 ` [RFC PATCH v11 0/5] blk-iocost: BPF struct_ops cost model Alexei Starovoitov
2026-10-28 20:09 ` Tejun Heo
2026-10-29 9:55 ` Tao Cui
2026-10-28 20:09 ` Tejun Heo
2026-10-29 9:57 ` 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=049090ed-48f8-4360-91f2-381357a0d40f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox