From: Tao Cui <cui.tao@linux.dev>
To: tj@kernel.org, josef@toxicopanda.com, axboe@kernel.dk, hch@infradead.org
Cc: cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, cui.tao@linux.dev,
cuitao@kylinos.cn
Subject: [PATCH v2 2/4] blk-iocost: charge zone appends as page-counted sequential writes
Date: Wed, 16 Sep 2026 16:53:02 +0800 [thread overview]
Message-ID: <20260916085304.1080271-3-cui.tao@linux.dev> (raw)
In-Reply-To: <20260916085304.1080271-1-cui.tao@linux.dev>
From: Tao Cui <cuitao@kylinos.cn>
Zone append is a primary write operation for zoned devices; zoned
btrfs and f2fs use it for data writes. It is priced at zero, so the
zone append portion of zoned workloads runs outside the controller:
a 1%-weight cgroup issued 16000 appends at zero cost on a zoned
null_blk.
A zone append advances the zone write pointer and is therefore
sequential from the device's perspective; the actual sector is only
returned after completion, so the cursor-based seq/rand
classification doesn't apply. Price it as a page-counted sequential
write. After this patch, 16000 appends from the same cgroup are
charged 533264 usec (33us per append).
Also skip the cursor update for ZA bios: bi_sector is the zone
start, not the actual write position (which is only returned after
completion). Setting the cursor from ZA would misclassify subsequent
READ/WRITE bios.
Fixes: 7caa47151ab2 ("blkcg: implement blk-iocost")
Signed-off-by: Tao Cui <cuitao@kylinos.cn>
---
block/blk-iocost.c | 15 +++++++++++++--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/block/blk-iocost.c b/block/blk-iocost.c
index 082f26d6e27b6..2e4e9ce2c9359 100644
--- a/block/blk-iocost.c
+++ b/block/blk-iocost.c
@@ -2560,6 +2560,17 @@ static void calc_vtime_cost_builtin(struct bio *bio, struct ioc_gq *iocg,
coef_randio = ioc->params.lcoefs[LCOEF_WRANDIO];
coef_page = ioc->params.lcoefs[LCOEF_WPAGE];
break;
+ case REQ_OP_ZONE_APPEND:
+ /*
+ * A zone append advances the zone write pointer and is
+ * therefore sequential from the device's perspective, so
+ * the cursor-based classification below doesn't apply.
+ * Compute the full cost here.
+ */
+ if (!is_merge)
+ cost += ioc->params.lcoefs[LCOEF_WSEQIO];
+ cost += pages * ioc->params.lcoefs[LCOEF_WPAGE];
+ goto out;
default:
goto out;
}
@@ -2720,8 +2731,8 @@ static void ioc_rqos_throttle(struct rq_qos *rqos, struct bio *bio)
if (!iocg_activate(iocg, &now))
return;
- /* dataless bios have no meaningful position for seq/rand detection */
- if (bio->bi_iter.bi_size)
+ /* ZA bi_sector is zone start, dataless bios have no write position */
+ if (bio->bi_iter.bi_size && bio_op(bio) != REQ_OP_ZONE_APPEND)
iocg->cursor = bio_end_sector(bio);
vtime = atomic64_read(&iocg->vtime);
cost = adjust_inuse_and_calc_cost(iocg, vtime, abs_cost, &now);
--
2.43.0
next prev parent reply other threads:[~2026-09-16 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 8:53 [PATCH v2 0/4] blk-iocost: charge flushes and zone appends Tao Cui
2026-09-16 8:53 ` [PATCH v2 1/4] blk-iocost: charge flushes as pageless random writes Tao Cui
2026-09-16 8:53 ` Tao Cui [this message]
2026-09-16 8:53 ` [PATCH v2 3/4] blk-iocost: account zone append completions in latency stats Tao Cui
2026-09-16 8:53 ` [PATCH v2 4/4] blk-iocost: fix stale comment in ioc_rqos_throttle() 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=20260916085304.1080271-3-cui.tao@linux.dev \
--to=cui.tao@linux.dev \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=cuitao@kylinos.cn \
--cc=hch@infradead.org \
--cc=josef@toxicopanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®