From: Christoph Hellwig <hch@lst.de>
To: Sam Protsenko <semen.protsenko@linaro.org>
Cc: Christoph Hellwig <hch@lst.de>,
axboe@kernel.dk, linux-block@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] block: remove the ioprio field from struct request
Date: Tue, 26 Nov 2024 07:52:53 +0100 [thread overview]
Message-ID: <20241126065253.GB1133@lst.de> (raw)
In-Reply-To: <CAPLW+4=kuHze3=+g80CsY6OkLno5gyjRfMWLXTFHu3N_=XcmqA@mail.gmail.com>
Hi Sam,
please try the patch below:
diff --git a/block/mq-deadline.c b/block/mq-deadline.c
index acdc28756d9d..91b3789f710e 100644
--- a/block/mq-deadline.c
+++ b/block/mq-deadline.c
@@ -685,10 +685,9 @@ static void dd_insert_request(struct blk_mq_hw_ctx *hctx, struct request *rq,
prio = ioprio_class_to_prio[ioprio_class];
per_prio = &dd->per_prio[prio];
- if (!rq->elv.priv[0]) {
+ if (!rq->elv.priv[0])
per_prio->stats.inserted++;
- rq->elv.priv[0] = (void *)(uintptr_t)1;
- }
+ rq->elv.priv[0] = per_prio;
if (blk_mq_sched_try_insert_merge(q, rq, free))
return;
@@ -753,18 +752,14 @@ static void dd_prepare_request(struct request *rq)
*/
static void dd_finish_request(struct request *rq)
{
- struct request_queue *q = rq->q;
- struct deadline_data *dd = q->elevator->elevator_data;
- const u8 ioprio_class = dd_rq_ioclass(rq);
- const enum dd_prio prio = ioprio_class_to_prio[ioprio_class];
- struct dd_per_prio *per_prio = &dd->per_prio[prio];
+ struct dd_per_prio *per_prio = rq->elv.priv[0];
/*
* The block layer core may call dd_finish_request() without having
* called dd_insert_requests(). Skip requests that bypassed I/O
* scheduling. See also blk_mq_request_bypass_insert().
*/
- if (rq->elv.priv[0])
+ if (per_prio)
atomic_inc(&per_prio->stats.completed);
}
next prev parent reply other threads:[~2024-11-26 6:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241112183746epcas5p40dcbbbd42a0f0be597193bf0808f8e67@epcas5p4.samsung.com>
2024-11-12 17:00 ` remove two fields from struct request Christoph Hellwig
2024-11-12 17:00 ` [PATCH 1/2] block: remove the write_hint field " Christoph Hellwig
2024-11-12 18:29 ` Bart Van Assche
2024-11-12 18:32 ` Bart Van Assche
2024-11-12 17:00 ` [PATCH 2/2] block: remove the ioprio " Christoph Hellwig
2024-11-12 18:22 ` John Garry
2024-11-13 5:06 ` Christoph Hellwig
2024-11-12 18:32 ` Bart Van Assche
2024-11-22 5:04 ` Sam Protsenko
2024-11-22 12:04 ` Christoph Hellwig
2024-11-22 21:55 ` Sam Protsenko
2024-11-22 22:18 ` Bart Van Assche
2024-11-25 23:13 ` Sam Protsenko
2024-11-25 7:36 ` Christoph Hellwig
2024-11-26 1:37 ` Sam Protsenko
2024-11-26 6:52 ` Christoph Hellwig [this message]
2024-11-26 7:37 ` Sam Protsenko
2024-11-12 18:29 ` remove two fields " Nitesh Shetty
2024-11-12 21:43 ` 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=20241126065253.GB1133@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=semen.protsenko@linaro.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).