mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shawn Lin <shawn.lin@rock-chips.com>
To: Ulf Hansson <ulfh@kernel.org>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
	linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shawn Lin <shawn.lin@rock-chips.com>
Subject: [PATCH] mmc: dw_mmc: enable MMC_CAP_DONE_COMPLETE
Date: Tue, 13 Oct 2026 15:24:04 +0800	[thread overview]
Message-ID: <1791876245-190981-1-git-send-email-shawn.lin@rock-chips.com> (raw)

All requests issued by dw_mmc are completed from dw_mci_work_func(),
which runs from the system_bh_wq workqueue. It is therefore preemptible
context and host->lock is dropped before the completion, see
mmc_request_done() in dw_mci_request_end().

The dw_mci_interrupt and the dw_mci_watchdog_fn never call mmc_request_done()
directly. So every request is completed from a sleepable context with no
spinlock held.

This is exactly the contract required by MMC_CAP_DONE_COMPLETE, which was
introduced for hosts that can complete requests within mmc_request_done()
without deferring to the core's complete_work.

Without the flag, the core records the finished request in
mq->complete_req and queues mq->complete_work, i.e. a second workqueue
dispatch plus an extra context switch per request. With the flag,
mmc_blk_mq_req_done() completes the request directly via
mmc_blk_mq_post_req() -> blk_mq_complete_request(), and a following
request completes the previous one inline from mmc_blk_rw_wait().

Measured on an RK3576 SD card (dw_mmc) with:

  perf record -a -g -F 999 -- sleep 30
  perf report --stdio -g graph,0.5,caller

fio: 4k randread, ioengine=libaio

Without the flag, the completion hot path is:

  mmc_request_done -> mmc_blk_mq_req_done -> queue_work_on      (~4.3%)
  ... -> mmc_blk_mq_complete_work            (kworker/5:1H-mm, ~18.4%)
       -> mmc_blk_mq_complete_prev_req -> mmc_blk_mq_post_req

with the flag the workqueue round trip disappears completely: there is no
queue_work_on and no mmc_blk_mq_complete_work in the profile anymore, and
the previous request is completed inline:

  mmc_blk_mq_issue_rq -> mmc_blk_mq_post_req -> mmc_blk_mq_complete_rq
                                                  -> __blk_mq_end_request

This can remove a redundant workqueue dispatch and context switch per completed
request.

Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
---

 drivers/mmc/host/dw_mmc.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c
index ff0b25d..bec777b 100644
--- a/drivers/mmc/host/dw_mmc.c
+++ b/drivers/mmc/host/dw_mmc.c
@@ -2945,6 +2945,8 @@ static int dw_mci_init_host_caps(struct dw_mci *host)
 	if (mmc->caps & MMC_CAP_SDIO_IRQ)
 		mmc->caps2 |= MMC_CAP2_SDIO_IRQ_NOTHREAD;
 
+	mmc->caps |= MMC_CAP_DONE_COMPLETE;
+
 	return 0;
 }
 
-- 
2.7.4


             reply	other threads:[~2026-10-13  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13  7:24 Shawn Lin [this message]
2026-10-28 17:16 ` Ulf Hansson
     [not found] ` <CGME20261110192834eucas1p1e183345528f097cb64340f36a03e4b14@eucas1p1.samsung.com>
2026-11-10 19:28   ` Marek Szyprowski

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=1791876245-190981-1-git-send-email-shawn.lin@rock-chips.com \
    --to=shawn.lin@rock-chips.com \
    --cc=jh80.chung@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ulfh@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

all inboxes | Powered by JetHome®