mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Ed Tsai <ed.tsai@mediatek.com>
Cc: matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, kbusch@kernel.org,
	amergnat@baylibre.com, liusong@linux.alibaba.com,
	wsd_upstream@mediatek.com, peter.wang@mediatek.com,
	stanley.chu@mediatek.com, powen.kao@mediatek.com,
	alice.chao@mediatek.com, naomi.chu@mediatek.com,
	Chun-Hung.Wu@mediatek.com
Subject: Re: [PATCH v3] blk-mq: check on cpu id when there is only one ctx mapping
Date: Wed, 14 Jun 2023 11:11:51 -0600	[thread overview]
Message-ID: <168676271101.1830690.9612621068004159159.b4-ty@kernel.dk> (raw)
In-Reply-To: <20230614002529.6636-1-ed.tsai@mediatek.com>


On Wed, 14 Jun 2023 08:25:29 +0800, Ed Tsai wrote:
> commit f168420c62e7 ("blk-mq: don't redirect completion for hctx withs
> only one ctx mapping") When nvme applies a 1:1 mapping of hctx and ctx,
> there will be no remote request.
> 
> But for ufs, the submission and completion queues could be asymmetric.
> (e.g. Multiple SQs share one CQ) Therefore, 1:1 mapping of hctx and
> ctx won't complete request on the submission cpu. In this situation,
> this nr_ctx check could violate the QUEUE_FLAG_SAME_FORCE, as a result,
> check on cpu id when there is only one ctx mapping.
> 
> [...]

Applied, thanks!

[1/1] blk-mq: check on cpu id when there is only one ctx mapping
      commit: 30654614f3d27230200b1650f6025a2ce67900b4

Best regards,
-- 
Jens Axboe




      parent reply	other threads:[~2023-06-14 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14  0:25 Ed Tsai
2023-06-14  6:19 ` Christoph Hellwig
2023-06-14 17:11 ` Jens Axboe [this message]

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=168676271101.1830690.9612621068004159159.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Chun-Hung.Wu@mediatek.com \
    --cc=alice.chao@mediatek.com \
    --cc=amergnat@baylibre.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=ed.tsai@mediatek.com \
    --cc=kbusch@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=liusong@linux.alibaba.com \
    --cc=matthias.bgg@gmail.com \
    --cc=naomi.chu@mediatek.com \
    --cc=peter.wang@mediatek.com \
    --cc=powen.kao@mediatek.com \
    --cc=stanley.chu@mediatek.com \
    --cc=wsd_upstream@mediatek.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

all inboxes | Powered by JetHome®