public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Tejun Heo <tj@kernel.org>,
	ming.lei@redhat.com
Subject: Re: [PATCH] block: sync mixed merged request's failfast with 1st bio's
Date: Tue, 14 Feb 2023 23:05:29 +0800	[thread overview]
Message-ID: <Y+ujOTfaesHzErb7@T590> (raw)
In-Reply-To: <20230209125527.667004-1-ming.lei@redhat.com>

On Thu, Feb 09, 2023 at 08:55:27PM +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:
> 
> 1) initially RA bio doesn't set failfast, however bio merge code
> doesn't consider this point, and just check its failfast setting for
> deciding if mixed merge is required. Fix this issue by adding helper
> of bio_failfast().
> 
> 2) when merging bio to request front, if this request is mixed
> merged, we have to sync request's faifast setting with 1st bio's
> failfast. Fix it by calling blk_update_mixed_merge().
> 
> 3) when merging bio to request back, if this request is mixed
> merged, we have to mark the bio as failfast, because blk_update_request
> simply updates request failfast with 1st bio's failfast. Fix
> it by calling blk_update_mixed_merge().
> 
> Fixes one normal EXT4 READ IO failure issue, because it is observed
> that the normal READ IO is merged with RA IO, and the mixed merged
> request has different failfast setting with 1st bio's, so finally
> the normal READ IO doesn't get retried.
> 
> Cc: Tejun Heo <tj@kernel.org>
> Fixes: 80a761fd33cf ("block: implement mixed merge of different failfast requests")
> Signed-off-by: Ming Lei <ming.lei@redhat.com>
> ---
>  block/blk-merge.c | 35 +++++++++++++++++++++++++++++++++--
>  1 file changed, 33 insertions(+), 2 deletions(-)

Hi Tejun, Jens and Guys,

Any chance to take a look? The patch addresses one RH customer issue.


Thanks, 
Ming


  reply	other threads:[~2023-02-14 15:06 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 [this message]
2023-02-16  3:25 ` Jens Axboe

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=Y+ujOTfaesHzErb7@T590 \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --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