From: Wu Bo <wubo.oduw@gmail.com>
To: Bart Van Assche <bvanassche@acm.org>, Wu Bo <bo.wu@vivo.com>
Cc: axboe@kernel.dk, dlemoal@kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH stable] block/mq-deadline: fix different priority request on the same zone
Date: Sat, 18 May 2024 08:52:54 +0800 [thread overview]
Message-ID: <a65ca1ef-1c9a-4d40-8e11-d9dc2cc75e1e@gmail.com> (raw)
In-Reply-To: <a1da2c7e-1b29-49cf-a45f-255d3b8b0da2@acm.org>
On 2024/5/18 01:53, Bart Van Assche wrote:
> On 5/16/24 18:44, Wu Bo wrote:
>> So I figured this solution to fix this priority issue on zoned
>> device. It sure
>> raises the overhead but can do fix it.
>
> Something I should have realized earlier is that this patch is not
> necessary with the latest upstream kernel (v6.10-rc1). Damien's zoned
> write plugging patch series has been merged. Hence, I/O schedulers,
> including the mq-deadline I/O schedulers, will only see a single
> zoned write at a time per zone. So it is no longer possible that
> zoned writes are reordered by the I/O scheduler because of their I/O
> priorities.
Hi Bart,
Yes, I noticed that 'zone write plugging' has been merged to latest
branch. But it seems hard to backport to old version which mq-deadline
priority feature has been merged. So is it possible to apply this fix to
old versions?
Thanks,
Wu Bo
>
> Thanks,
>
> Bart.
next prev parent reply other threads:[~2024-05-18 0:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 9:28 [PATCH stable] block/mq-deadline: fix different priority request on the same zone Wu Bo
2024-05-16 13:45 ` Bart Van Assche
2024-05-17 1:44 ` Wu Bo
2024-05-17 17:53 ` Bart Van Assche
2024-05-18 0:52 ` Wu Bo [this message]
2024-05-18 2:14 ` Bart Van Assche
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=a65ca1ef-1c9a-4d40-8e11-d9dc2cc75e1e@gmail.com \
--to=wubo.oduw@gmail.com \
--cc=axboe@kernel.dk \
--cc=bo.wu@vivo.com \
--cc=bvanassche@acm.org \
--cc=dlemoal@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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