From: Bob Liu <bob.liu@oracle.com>
To: Dmitry Fomichev <Dmitry.Fomichev@wdc.com>,
Christoph Hellwig <hch@infradead.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>,
Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: Re: [PATCH] block: streamline merge possibility checks
Date: Thu, 9 Jan 2020 08:56:41 +0800 [thread overview]
Message-ID: <4dea4331-9de3-e6b7-c453-05f9baeaec00@oracle.com> (raw)
In-Reply-To: <BN8PR04MB643390C7263ACE2AFBDF5917E13E0@BN8PR04MB6433.namprd04.prod.outlook.com>
On 1/9/20 6:02 AM, Dmitry Fomichev wrote:
>> -----Original Message-----
>> From: Christoph Hellwig <hch@infradead.org>
>> Sent: Wednesday, January 8, 2020 8:45 AM
>> To: Bob Liu <bob.liu@oracle.com>
>> Cc: Dmitry Fomichev <Dmitry.Fomichev@wdc.com>; linux-
>> block@vger.kernel.org; Jens Axboe <axboe@kernel.dk>; Damien Le Moal
>> <Damien.LeMoal@wdc.com>
>> Subject: Re: [PATCH] block: streamline merge possibility checks
>>
>> On Fri, Dec 20, 2019 at 02:50:05PM +0800, Bob Liu wrote:
>>> On 12/19/19 3:41 AM, Dmitry Fomichev wrote:
>>>> Checks for data direction in attempt_merge() and blk_rq_merge_ok()
>>>
>>> Speak about these two functions, do you think attempt_merge() can be
>> built on blk_rq_merge_ok()?
>>> Things like..
>>> diff --git a/block/blk-merge.c b/block/blk-merge.c
>>> index 48e6725..2a00c4c 100644
>>> --- a/block/blk-merge.c
>>> +++ b/block/blk-merge.c
>>> @@ -724,28 +724,7 @@ static enum elv_merge blk_try_req_merge(struct
>> request *req,
>>> static struct request *attempt_merge(struct request_queue *q,
>>> struct request *req, struct request *next)
>>> {
>>> - if (!rq_mergeable(req) || !rq_mergeable(next))
>>> - return NULL;
>>> -
>>> - if (req_op(req) != req_op(next))
>>> - return NULL;
>>> -
>>> - if (rq_data_dir(req) != rq_data_dir(next)
>>> - || req->rq_disk != next->rq_disk)
>>> - return NULL;
>>> -
>>> - if (req_op(req) == REQ_OP_WRITE_SAME &&
>>> - !blk_write_same_mergeable(req->bio, next->bio))
>>> - return NULL;
>>> -
>>> - /*
>>> - * Don't allow merge of different write hints, or for a hint with
>>> - * non-hint IO.
>>> - */
>>> - if (req->write_hint != next->write_hint)
>>> - return NULL;
>>> -
>>> - if (req->ioprio != next->ioprio)
>>> + if (!blk_rq_merge_ok(req, next->bio))
>>> return NULL;
>>
>> This looks sensible, but we might have to be a bit more careful.
>> rq_mergeable checks for RQF_NOMERGE_FLAGS and various ops, while
>> bio_mergeable is missing those. So I think you need to go through
>> carefully if we need to keep any extra checks, but otherwise using
>> blk_rq_merge_ok looks sensible.
>
> I tried this patch as is and, indeed, it leads to blktests failures and filesystem
> errors, apparently because of the RQF_NOMERGE_FLAGS difference.
> However, the patch below seems to work - I've been running my host system
> with it for a couple of days with no issues. This one is added on top of
> "block: streamline merge possibility checks" patch.
>
> From: Dmitry Fomichev <dmitry.fomichev@wdc.com>
> Date: Wed, 8 Jan 2020 14:24:06 -0500
> Subject: [PATCH] block: simplify merge checks
>
> The code parts to decide on merge possibility in attempt_merge() and
> blk_rq_merge_ok() look very similar. It is possible to move these
> checks to a common inline helper function.
>
> Suggested-by: Bob Liu <bob.liu@oracle.com>
> Signed-off-by: Dmitry Fomichev <dmitry.fomichev@wdc.com>
> ---
> block/blk-merge.c | 56 +++++++++++++++++++++++++++--------------------
> 1 file changed, 32 insertions(+), 24 deletions(-)
>
> diff --git a/block/blk-merge.c b/block/blk-merge.c
> index f68d67b367d6..49052a53051f 100644
> --- a/block/blk-merge.c
> +++ b/block/blk-merge.c
> @@ -732,6 +732,36 @@ static enum elv_merge blk_try_req_merge(struct request *req,
> return ELEVATOR_NO_MERGE;
> }
>
> +static inline bool blk_rq_mergeable(struct request *rq, struct bio *bio)
> +{
> + if (!rq_mergeable(rq))
> + return false;
> +
> + if (req_op(rq) != bio_op(bio))
> + return false;
> +
> + /* must be same device */
> + if (rq->rq_disk != bio->bi_disk)
> + return false;
> +
> + /* must be using the same buffer */
> + if (req_op(rq) == REQ_OP_WRITE_SAME &&
> + !blk_write_same_mergeable(rq->bio, bio))
> + return false;
> +
> + /*
> + * Don't allow merge of different write hints, or for a hint with
> + * non-hint IO.
> + */
> + if (rq->write_hint != bio->bi_write_hint)
> + return false;
> +
> + if (rq->ioprio != bio_prio(bio))
> + return false;
> +
> + return true;
> +}
> +
> /*
> * For non-mq, this has to be called with the request spinlock acquired.
> * For mq with scheduling, the appropriate queue wide lock should be held.
> @@ -739,7 +769,7 @@ static enum elv_merge blk_try_req_merge(struct request *req,
> static struct request *attempt_merge(struct request_queue *q,
> struct request *req, struct request *next)
> {
> - if (!blk_rq_merge_ok(req, next->bio))
> + if (!rq_mergeable(next) || !blk_rq_mergeable(req, next->bio))
> return NULL;
>
> /*
> @@ -841,35 +871,13 @@ int blk_attempt_req_merge(struct request_queue *q, struct request *rq,
>
> bool blk_rq_merge_ok(struct request *rq, struct bio *bio)
> {
> - if (!rq_mergeable(rq) || !bio_mergeable(bio))
> - return false;
> -
> - if (req_op(rq) != bio_op(bio))
> - return false;
> -
> - /* must be same device */
> - if (rq->rq_disk != bio->bi_disk)
> + if (!bio_mergeable(bio) || !blk_rq_mergeable(rq, bio))
> return false;
>
Nitpick, I think bio_mergeable(bio) can also put inside blk_rq_mergeable().
Anyway, looks fine to me, thanks!
Reviewed-by: Bob Liu <bob.liu@oracle.com>
> /* only merge integrity protected bio into ditto rq */
> if (blk_integrity_merge_bio(rq->q, rq, bio) == false)
> return false;
>
> - /* must be using the same buffer */
> - if (req_op(rq) == REQ_OP_WRITE_SAME &&
> - !blk_write_same_mergeable(rq->bio, bio))
> - return false;
> -
> - /*
> - * Don't allow merge of different write hints, or for a hint with
> - * non-hint IO.
> - */
> - if (rq->write_hint != bio->bi_write_hint)
> - return false;
> -
> - if (rq->ioprio != bio_prio(bio))
> - return false;
> -
> return true;
> }
>
>
next prev parent reply other threads:[~2020-01-09 1:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 19:41 [PATCH] block: streamline merge possibility checks Dmitry Fomichev
2019-12-19 8:56 ` Bob Liu
2019-12-19 10:05 ` Damien Le Moal
2019-12-20 6:50 ` Bob Liu
2020-01-08 13:44 ` Christoph Hellwig
2020-01-08 22:02 ` Dmitry Fomichev
2020-01-09 0:56 ` Bob Liu [this message]
2020-01-08 13:41 ` Christoph Hellwig
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=4dea4331-9de3-e6b7-c453-05f9baeaec00@oracle.com \
--to=bob.liu@oracle.com \
--cc=Damien.LeMoal@wdc.com \
--cc=Dmitry.Fomichev@wdc.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).