Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   "Martin K. Petersen" <martin.petersen@oracle.com>
To:     John Garry <john.garry@huawei.com>, jejb@linux.ibm.com
Cc:     "Martin K . Petersen" <martin.petersen@oracle.com>,
        linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH v2] scsi: core: Refine how we set tag_set NUMA node
Date:   Mon,  2 May 2022 20:51:33 -0400
Message-Id: <165153836362.24053.7061141693570031456.b4-ty@oracle.com>
In-Reply-To: <1648640315-21419-1-git-send-email-john.garry@huawei.com>
References: <1648640315-21419-1-git-send-email-john.garry@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 30 Mar 2022 19:38:35 +0800, John Garry wrote:

> For SCSI hosts which enable host_tagset the NUMA node returned from
> blk_mq_hw_queue_to_node() is NUMA_NO_NODE always. Then, since in
> scsi_mq_setup_tags() the default we choose for the tag_set NUMA node is
> NUMA_NO_NODE, we always evaluate the NUMA node as NUMA_NO_NODE in
> functions like blk_mq_alloc_rq_map().
> 
> The reason we get NUMA_NO_NODE from blk_mq_hw_queue_to_node() is that
> the hctx_idx passed is BLK_MQ_NO_HCTX_IDX - so we can't match against a
> (HW) queue mapping index.
> 
> [...]

Applied to 5.19/scsi-queue, thanks!

[1/1] scsi: core: Refine how we set tag_set NUMA node
      https://git.kernel.org/mkp/scsi/c/973dac8a8a14

-- 
Martin K. Petersen	Oracle Linux Engineering