[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168676271101.1830690.9612621068004159159.b4-ty@kernel.dk>
Date: Wed, 14 Jun 2023 11:11:51 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Ed Tsai <ed.tsai@...iatek.com>
Cc: matthias.bgg@...il.com, angelogioacchino.delregno@...labora.com,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, kbusch@...nel.org,
amergnat@...libre.com, liusong@...ux.alibaba.com,
wsd_upstream@...iatek.com, peter.wang@...iatek.com,
stanley.chu@...iatek.com, powen.kao@...iatek.com,
alice.chao@...iatek.com, naomi.chu@...iatek.com,
Chun-Hung.Wu@...iatek.com
Subject: Re: [PATCH v3] blk-mq: check on cpu id when there is only one ctx
mapping
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
Powered by blists - more mailing lists