public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christian Löhle" <CLoehle@hyperstone.com>
To: "ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
	"axboe@kernel.dk" <axboe@kernel.dk>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Cc: Avri Altman <Avri.Altman@wdc.com>,
	"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
	"vincent.whitchurch@axis.com" <vincent.whitchurch@axis.com>
Subject: [PATCHv2 1/3] block: Requeue req as head if driver touched it
Date: Mon, 14 Nov 2022 15:29:00 +0000	[thread overview]
Message-ID: <2c8d249c6bb74d688a625654559bacbb@hyperstone.com> (raw)

In case the driver set RQF_DONTPREP flag, requeue the request as head as
it is likely that the backing storage already had a request to an
adjacent region, so getting the requeued request out as soon as possible
may give us some performance benefit.

The are various reasons a driver may requeue a request
(and therefore RQF_DONTPREP being set).
One reason may be that the driver or the hardware cannot satisfy
the block layer alignment/sizes.

This for example is the case with mmcblk with a host driver that
cannot deal with multiple block transfers.
Consider a request for lba 42 for one page so 4K or 8 blocks.
mmcblk will do a single block request for lba 42 and requeue for
the rest if the host can only perform single block transfers.
In this case the device only delivered 512 bytes of data at lba 42,
but may have performed a readahead itself for the following lbas,
or do an 'implicit' readahead as it only deals with larger block
size mappings itself.
In that case it would be beneificial if the request for lba 43 and
the rest of the remaining blocks follow immediately after the initial
lba 42 request.
Requeueing already partially processed requests as head preserves the
intended request order (unless the driver has a queue of its own)
and therefore mitigates this problem .

Signed-off-by: Christian Loehle <cloehle@hyperstone.com>
---
-v2: Extended commit message with example use case, no code change

 block/blk-mq.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/block/blk-mq.c b/block/blk-mq.c
index 33292c01875d..d863c826fb23 100644
--- a/block/blk-mq.c
+++ b/block/blk-mq.c
@@ -1429,7 +1429,7 @@ static void blk_mq_requeue_work(struct work_struct *work)
 		 * merge.
 		 */
 		if (rq->rq_flags & RQF_DONTPREP)
-			blk_mq_request_bypass_insert(rq, false, false);
+			blk_mq_request_bypass_insert(rq, true, false);
 		else
 			blk_mq_sched_insert_request(rq, true, false, false);
 	}
-- 
2.37.3
Hyperstone GmbH | Reichenaustr. 39a  | 78467 Konstanz
Managing Director: Dr. Jan Peter Berns.
Commercial register of local courts: Freiburg HRB381782


             reply	other threads:[~2022-11-14 15:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 15:29 Christian Löhle [this message]
2022-11-16 12:52 ` [PATCHv2 1/3] block: Requeue req as head if driver touched it Ulf Hansson

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=2c8d249c6bb74d688a625654559bacbb@hyperstone.com \
    --to=cloehle@hyperstone.com \
    --cc=Avri.Altman@wdc.com \
    --cc=adrian.hunter@intel.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=vincent.whitchurch@axis.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