lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165153836362.24053.7061141693570031456.b4-ty@oracle.com>
Date:   Mon,  2 May 2022 20:51:33 -0400
From:   "Martin K. Petersen" <martin.petersen@...cle.com>
To:     John Garry <john.garry@...wei.com>, jejb@...ux.ibm.com
Cc:     "Martin K . Petersen" <martin.petersen@...cle.com>,
        linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH v2] scsi: core: Refine how we set tag_set NUMA node

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ