From: Tejun Heo <tj@kernel.org>
To: Tao Cui <cui.tao@linux.dev>
Cc: 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 2/4] selftests/bpf: add iocost cost model test
Date: Fri, 16 Oct 2026 07:49:56 -1000 [thread overview]
Message-ID: <47611e3e8a2bfbdce1dfd9a1fe2c5019@kernel.org> (raw)
In-Reply-To: <20261003124045.1289305-3-cui.tao@linux.dev>
Hello, Tao.
On Sat, 03 Oct 2026 20:40:43 +0800, Tao Cui wrote:
> + dev = getenv("IOCOST_TEST_DEV");
Nothing in the tree sets IOCOST_TEST_DEV, so both tests always skip in CI.
The null_blk instance the v11 removal test creates could serve these two
as well.
> + if (ASSERT_OK(err, "readback"))
> + ASSERT_EQ(strcmp(model, "bpf"), 0, "model_bpf");
ASSERT_STREQ() prints both strings on failure.
> + bpf_link__destroy(skel->links.iocost_2x);
> + /* cleared, or the skeleton destroy below detaches again */
> + skel->links.iocost_2x = NULL;
Without clearing, the skeleton destroy would call bpf_link__destroy() on
the freed link. It wouldn't detach again.
> + * The cursor handling follows the builtin: a zero cursor means "no
> + * previous IO", and the cursor is advanced for bios the builtin
> + * prices (READ/WRITE with a non-zero size; the builtin skips the
> + * whole update when the cost is zero), so flushes and discards
> + * leave it alone and long merged streams do not drift past the
> + * 16MB seek threshold.
The model advances the cursor for every merged READ or WRITE bio.
ioc_rqos_merge() only moves it on a back merge into the request ending at
the cursor, so a front merge leaves the builtin's cursor alone and moves
the model's.
> + } else {
> + base = randio;
> + for (i = 1; i < NSLOTS; i++) {
> + if (s->stamp[i] < s->stamp[victim])
> + victim = i;
> + }
A merged bio which matches no slot, e.g. a front merge or a merge into
another stream's request, takes the LRU slot and can evict a live stream.
Maybe skip the slot replacement for IOCOST_COST_F_MERGE?
Thanks.
--
tejun
next prev parent reply other threads:[~2026-10-16 17:49 UTC|newest]
Thread overview: 14+ 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-03 12:40 ` [RFC PATCH v10 2/4] selftests/bpf: add iocost cost model test Tao Cui
2026-10-16 17:49 ` Tejun Heo [this message]
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-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-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
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=47611e3e8a2bfbdce1dfd9a1fe2c5019@kernel.org \
--to=tj@kernel.org \
--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=cui.tao@linux.dev \
--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 \
/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