aboutsummaryrefslogtreecommitdiff
path: root/include/linux/blktrace_api.h
diff options
context:
space:
mode:
authorEd Tsai <ed.tsai@mediatek.com>2023-06-14 08:25:29 +0800
committerJens Axboe <axboe@kernel.dk>2023-06-14 11:11:25 -0600
commit30654614f3d27230200b1650f6025a2ce67900b4 (patch)
tree9f8284d7566cacc1e4428be18e6a29276cc1b794 /include/linux/blktrace_api.h
parent6070131176af5375ae9fa24efebda41c878f4ec2 (diff)
downloadlinux-30654614f3d27230200b1650f6025a2ce67900b4.tar.gz
linux-30654614f3d27230200b1650f6025a2ce67900b4.tar.bz2
linux-30654614f3d27230200b1650f6025a2ce67900b4.zip
blk-mq: check on cpu id when there is only one ctx mapping
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. Signed-off-by: Ed Tsai <ed.tsai@mediatek.com> Signed-off-by: Po-Wen Kao <powen.kao@mediatek.com> Suggested-by: Keith Busch <kbusch@kernel.org> Reviewed-by: Christoph Hellwig <hch@lst.de> Link: https://lore.kernel.org/r/20230614002529.6636-1-ed.tsai@mediatek.com [axboe: fixed up indentation] Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'include/linux/blktrace_api.h')
0 files changed, 0 insertions, 0 deletions