From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <ming.lei@redhat.com>
Cc: linux-block@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH] block: sync mixed merged request's failfast with 1st bio's
Date: Wed, 15 Feb 2023 20:25:21 -0700 [thread overview]
Message-ID: <167651792171.207091.3077979859216146323.b4-ty@kernel.dk> (raw)
In-Reply-To: <20230209125527.667004-1-ming.lei@redhat.com>
On Thu, 09 Feb 2023 20:55:27 +0800, Ming Lei wrote:
> We support mixed merge for requests/bios with different fastfail
> settings. When request fails, each time we only handle the portion
> with same failfast setting, then bios with failfast can be failed
> immediately, and bios without failfast can be retried.
>
> The idea is pretty good, but the current implementation has several
> defects:
>
> [...]
Applied, thanks!
[1/1] block: sync mixed merged request's failfast with 1st bio's
commit: 3481d9424950159b1dbd366a14acab79f1440bbf
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-02-16 3:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 12:55 [PATCH] block: sync mixed merged request's failfast with 1st bio's Ming Lei
2023-02-14 15:05 ` Ming Lei
2023-02-16 3:25 ` 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=167651792171.207091.3077979859216146323.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--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