[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230912155249.113009-1-ptyadav@amazon.de>
Date: Tue, 12 Sep 2023 17:52:49 +0200
From: Pratyush Yadav <ptyadav@...zon.de>
To: Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...nel.dk>,
"Christoph Hellwig" <hch@....de>, Sagi Grimberg <sagi@...mberg.me>
CC: Pratyush Yadav <ptyadav@...zon.de>,
<linux-nvme@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: [PATCH v2] nvme-pci: do not set the NUMA node of device if it has none
If a device has no NUMA node information associated with it, the driver
puts the device in node first_memory_node (say node 0). Not having a
NUMA node and being associated with node 0 are completely different
things and it makes little sense to mix the two.
Signed-off-by: Pratyush Yadav <ptyadav@...zon.de>
---
Changes in v2:
- Re-worded the commit message.
drivers/nvme/host/pci.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 2f57da12d983..347cb5daebc3 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -2916,9 +2916,6 @@ static struct nvme_dev *nvme_pci_alloc_dev(struct pci_dev *pdev,
struct nvme_dev *dev;
int ret = -ENOMEM;
- if (node == NUMA_NO_NODE)
- set_dev_node(&pdev->dev, first_memory_node);
-
dev = kzalloc_node(sizeof(*dev), GFP_KERNEL, node);
if (!dev)
return ERR_PTR(-ENOMEM);
--
2.40.1
Powered by blists - more mailing lists