From: Jens Axboe <axboe@kernel.dk>
To: Xiao Ni <xni@redhat.com>
Cc: linux-block@vger.kernel.org, ming.lei@redhat.com
Subject: Re: [PATCH 1/1] block: Merge bio before checking ->cached_rq
Date: Thu, 09 Feb 2023 08:12:58 -0700 [thread overview]
Message-ID: <167595557892.325128.17846082603567400159.b4-ty@kernel.dk> (raw)
In-Reply-To: <20230209031930.27354-1-xni@redhat.com>
On Thu, 09 Feb 2023 11:19:30 +0800, Xiao Ni wrote:
> It checks if plug->cached_rq is empty before merging bio. But the merge action
> doesn't have relationship with plug->cached_rq, it trys to merge bio with
> requests within plug->mq_list. Now it checks if ->cached_rq is empty before
> merging bio. If it's empty, it will miss the merge chances. So move the merge
> function before checking ->cached_rq.
>
>
> [...]
Applied, thanks!
[1/1] block: Merge bio before checking ->cached_rq
commit: 23f3e3272e7a4d9fb870485cd6df1e4f9539282c
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-02-09 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 3:19 [PATCH 1/1] block: Merge bio before checking ->cached_rq Xiao Ni
2023-02-09 3:41 ` Ming Lei
2023-02-09 15:12 ` 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=167595557892.325128.17846082603567400159.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=xni@redhat.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