From: Damien Le Moal <dlemoal@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>, Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Yu Kuai <yukuai@kernel.org>, chengkaitao <chengkaitao@kylinos.cn>
Subject: Re: [PATCH 1/2] block/mq-deadline: Introduce dd_start_request()
Date: Tue, 14 Oct 2025 13:16:58 +0900 [thread overview]
Message-ID: <063353d7-9d79-461e-a974-4419a5b6421c@kernel.org> (raw)
In-Reply-To: <20251013192803.4168772-2-bvanassche@acm.org>
On 2025/10/14 4:28, Bart Van Assche wrote:
> Prepare for adding a second caller of this function. No functionality
> has been changed.
>
> Cc: Damien Le Moal <dlemoal@kernel.org>
> Cc: Yu Kuai <yukuai@kernel.org>
> Cc: chengkaitao <chengkaitao@kylinos.cn>
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
One nit below.
Other than that, looks fine to me.
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
> ---
> block/mq-deadline.c | 22 ++++++++++++++--------
> 1 file changed, 14 insertions(+), 8 deletions(-)
>
> diff --git a/block/mq-deadline.c b/block/mq-deadline.c
> index 3e741d33142d..647a45f6d935 100644
> --- a/block/mq-deadline.c
> +++ b/block/mq-deadline.c
> @@ -306,6 +306,19 @@ static bool started_after(struct deadline_data *dd, struct request *rq,
> return time_after(start_time, latest_start);
> }
>
> +static struct request *dd_start_request(struct deadline_data *dd,
> + enum dd_data_dir data_dir,
> + struct request *rq)
Why return the request that is passed ? Not sure that is necessary.
> +{
> + u8 ioprio_class = dd_rq_ioclass(rq);
> + enum dd_prio prio = ioprio_class_to_prio[ioprio_class];
> +
> + dd->per_prio[prio].latest_pos[data_dir] = blk_rq_pos(rq);
> + dd->per_prio[prio].stats.dispatched++;
> + rq->rq_flags |= RQF_STARTED;
> + return rq;
> +}
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2025-10-14 4:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 19:28 [PATCH 0/2] block/mq-deadline: Fix BLK_MQ_INSERT_AT_HEAD support Bart Van Assche
2025-10-13 19:28 ` [PATCH 1/2] block/mq-deadline: Introduce dd_start_request() Bart Van Assche
2025-10-14 4:16 ` Damien Le Moal [this message]
2025-10-14 15:47 ` Bart Van Assche
2025-10-13 19:28 ` [PATCH 2/2] block/mq-deadline: Switch back to a single dispatch list Bart Van Assche
2025-10-14 4:19 ` Damien Le Moal
2025-10-14 6:10 ` Yu Kuai
2025-10-14 15:55 ` Bart Van Assche
2025-10-14 13:12 ` [PATCH 0/2] block/mq-deadline: Fix BLK_MQ_INSERT_AT_HEAD support 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=063353d7-9d79-461e-a974-4419a5b6421c@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=chengkaitao@kylinos.cn \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=yukuai@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