From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: linux-block <linux-block@vger.kernel.org>
Subject: wbt_lat_usec still set despite wbt disabled by BFQ
Date: Wed, 17 Aug 2022 19:12:12 +0200 [thread overview]
Message-ID: <a5041479-f417-2b95-b645-56e665a7e557@applied-asynchrony.com> (raw)
I just noticed that my device configured with BFQ still shows wbt_lat_usec
as configured, despite the fact that BFQ disables WBT in bfq_init_queue [1]:
$cat /sys/block/sdc/queue/scheduler
mq-deadline [bfq] none
$cat /sys/block/sdc/queue/wbt_lat_usec
75000
Is this supposed to be 0 (since it's disabled) or is sysfs confused?
Thanks,
Holger
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/block/bfq-iosched.c#n7195
next reply other threads:[~2022-08-17 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 17:12 Holger Hoffstätte [this message]
2022-09-13 13:39 ` wbt_lat_usec still set despite wbt disabled by BFQ Yu Kuai
2022-09-13 14:12 ` Holger Hoffstätte
2022-09-13 14:20 ` Yu Kuai
2022-09-13 16:13 ` Holger Hoffstätte
2022-09-14 1:35 ` Yu Kuai
2022-09-14 6:05 ` Holger Hoffstätte
2022-09-14 9:23 ` Yu Kuai
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=a5041479-f417-2b95-b645-56e665a7e557@applied-asynchrony.com \
--to=holger@applied-asynchrony.com \
--cc=linux-block@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