From: Jens Axboe <axboe@kernel.dk>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
linux-block@vger.kernel.org
Cc: Bart Van Assche <bvanassche@acm.org>
Subject: Re: [PATCH 0/2] mq-deadline fixes
Date: Thu, 24 Nov 2022 06:30:05 -0700 [thread overview]
Message-ID: <166929660560.51429.3700435810079299475.b4-ty@kernel.dk> (raw)
In-Reply-To: <20221124021208.242541-1-damien.lemoal@opensource.wdc.com>
On Thu, 24 Nov 2022 11:12:06 +0900, Damien Le Moal wrote:
> A couple of patches to fix (1) a potential problem with mq-deadline IO
> priority handling and (2) to improve write performance with HDDs.
> While the performance improvement patch is technically not a bug fix,
> the improvement is so significant with some HDDs that I added cc-stable
> tag to get the patch added to LTS kernels.
>
> Damien Le Moal (2):
> block: mq-deadline: Fix dd_finish_request() for zoned devices
> block: mq-deadline: Do not break sequential write streams to zoned
> HDDs
>
> [...]
Applied, thanks!
[1/2] block: mq-deadline: Fix dd_finish_request() for zoned devices
commit: 2820e5d0820ac4daedff1272616a53d9c7682fd2
[2/2] block: mq-deadline: Do not break sequential write streams to zoned HDDs
commit: 015d02f48537cf2d1a65eeac50717566f9db6eec
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-11-24 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 2:12 [PATCH 0/2] mq-deadline fixes Damien Le Moal
2022-11-24 2:12 ` [PATCH 1/2] block: mq-deadline: Fix dd_finish_request() for zoned devices Damien Le Moal
2022-11-24 2:12 ` [PATCH 2/2] block: mq-deadline: Do not break sequential write streams to zoned HDDs Damien Le Moal
2022-11-24 7:51 ` [PATCH 0/2] mq-deadline fixes Johannes Thumshirn
2022-11-24 13:30 ` Jens Axboe [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=166929660560.51429.3700435810079299475.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@opensource.wdc.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