From: Vincent Fu <vincentfu@gmail.com>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
fio@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Cc: Damien Le Moal <dlemoal@kernel.org>,
Dmitry Fomichev <Dmitry.Fomichev@wdc.com>,
Niklas Cassel <niklas.cassel@wdc.com>
Subject: Re: [PATCH] t/zbd: set mq-deadline scheduler to device-mapper destination devices
Date: Tue, 26 Sep 2023 11:47:29 -0400 [thread overview]
Message-ID: <40a3c93d-686d-72d7-fba8-d87efd56c390@gmail.com> (raw)
In-Reply-To: <20230913015249.2226799-1-shinichiro.kawasaki@wdc.com>
On 9/12/23 21:52, Shin'ichiro Kawasaki wrote:
> When write workloads run on zoned block devices, mq-deadline scheduler is
> required to ensure write operations are sequential. To fulfill this
> requirement, the test script t/zbd/test-zbd-support sets mq-deadline to
> the sysfs attribute "queue/scheduler". However, this preparation does
> not work when the write target device is a bio based device-mapper
> device. The device is bio based then I/O scheduler does not work.
> Setting mq-deadline to the sysfs attribute has no effect. On top of
> that, the sysfs attribute "queue/scheduler" is no longer available for
> bio based device-mapper devices since Linux kernel version v6.5.
>
> To ensure mq-deadline scheduler for bio based device-mapper devices,
> improve the helper function set_io_scheduler. If the sysfs attribute
> "queue/scheduler" is available, use it. Otherwise, check if the test
> device is a zoned device-mapper (linear, flakey or crypt). If so, set
> mq-deadline scheduler to destination devices of the device-mapper
> device. To implement these, add some helper functions.
>
> Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Applied. Thanks.
Vincent
prev parent reply other threads:[~2023-09-26 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 1:52 [PATCH] t/zbd: set mq-deadline scheduler to device-mapper destination devices Shin'ichiro Kawasaki
2023-09-26 15:47 ` Vincent Fu [this message]
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=40a3c93d-686d-72d7-fba8-d87efd56c390@gmail.com \
--to=vincentfu@gmail.com \
--cc=Dmitry.Fomichev@wdc.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=fio@vger.kernel.org \
--cc=niklas.cassel@wdc.com \
--cc=shinichiro.kawasaki@wdc.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).